Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da2428f70b41252a7123d5bb934e091b5586aa52deb0d6b2a5be615af1832d80

Tx prefix hash: df9f94572e16e75c49e350e4a446fc81a8fca0b9401244ed9a79197942513b36
Tx public key: bcd88af8b6134cc558a8003cf72ceb21f7b47c318c3cf866beb6a2f2c75e3364
Timestamp: 1735505633 Timestamp [UCT]: 2024-12-29 20:53:53 Age [y:d:h:m:s]: 00:168:04:30:53
Block: 1185972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119943 RingCT/type: yes/0
Extra: 01bcd88af8b6134cc558a8003cf72ceb21f7b47c318c3cf866beb6a2f2c75e33640211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 647c7f7118713dbc56431e211c2441522749563b1f2d0ed7ec4196e39500aaba 0.600000000000 1672447 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": 1185982, "vin": [ { "gen": { "height": 1185972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "647c7f7118713dbc56431e211c2441522749563b1f2d0ed7ec4196e39500aaba" } } ], "extra": [ 1, 188, 216, 138, 248, 182, 19, 76, 197, 88, 168, 0, 60, 247, 44, 235, 33, 247, 180, 124, 49, 140, 60, 248, 102, 190, 182, 162, 242, 199, 94, 51, 100, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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