Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 955644d07adf725d772060dd97908a476e460c0b1edccdd5602696c6248fe563

Tx prefix hash: 7a8b67bf5c30e07ea8b2b3f763c763054ed95338f286b81334153b1de93cadd2
Tx public key: cae23ff8b4c4e8ae9a8b4aa7b516450aaeacd75a6ed4733db0d3e6957a537442
Timestamp: 1694487240 Timestamp [UCT]: 2023-09-12 02:54:00 Age [y:d:h:m:s]: 01:212:05:53:38
Block: 846224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412800 RingCT/type: yes/0
Extra: 01cae23ff8b4c4e8ae9a8b4aa7b516450aaeacd75a6ed4733db0d3e6957a537442021100000015faf35c9c000000000000000000

1 output(s) for total of 0.964070216000 dcy

stealth address amount amount idx
00: c1acb85a06ea38e7da560c6c83d23691714e8070f1a101bc0a98a622e7e0f6c5 0.964070216000 1299672 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 846234, "vin": [ { "gen": { "height": 846224 } } ], "vout": [ { "amount": 964070216, "target": { "key": "c1acb85a06ea38e7da560c6c83d23691714e8070f1a101bc0a98a622e7e0f6c5" } } ], "extra": [ 1, 202, 226, 63, 248, 180, 196, 232, 174, 154, 139, 74, 167, 181, 22, 69, 10, 174, 172, 215, 90, 110, 212, 115, 61, 176, 211, 230, 149, 122, 83, 116, 66, 2, 17, 0, 0, 0, 21, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8