Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd629c5028ac14f35ab5a05bf308281ba83b96888df1610025c9fd25d1fab1e9

Tx prefix hash: 78eee166e20c5e37771a00f1c34cd1582c8c39ddfc15295b760e4b7b496ac7d3
Tx public key: 33d50a3807c01cf0aa08ba9010dbe2078bbeedc08674d3ed92e7fd61495e9e48
Timestamp: 1713955674 Timestamp [UCT]: 2024-04-24 10:47:54 Age [y:d:h:m:s]: 00:357:19:29:48
Block: 1007446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255793 RingCT/type: yes/0
Extra: 0133d50a3807c01cf0aa08ba9010dbe2078bbeedc08674d3ed92e7fd61495e9e480211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7032e0fbc7e99f3a21ee311ecf78d5e228015683c57c0ad534656f29db2282b9 0.600000000000 1468786 of 15

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": 1007456, "vin": [ { "gen": { "height": 1007446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7032e0fbc7e99f3a21ee311ecf78d5e228015683c57c0ad534656f29db2282b9" } } ], "extra": [ 1, 51, 213, 10, 56, 7, 192, 28, 240, 170, 8, 186, 144, 16, 219, 226, 7, 139, 190, 237, 192, 134, 116, 211, 237, 146, 231, 253, 97, 73, 94, 158, 72, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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