Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a9a54571c658a1b730b79eb1fb605b87a28a465eeec257f318aa2650e65ea9b

Tx prefix hash: 372351aa258d2edfc96f17013d2cf4f6ac3a4b71303f8d2671e21230a1c0a0eb
Tx public key: 60f0a12b65467798c0225b500bfddd9fbac3635e1f819b6172b3930655e749d6
Timestamp: 1721700854 Timestamp [UCT]: 2024-07-23 02:14:14 Age [y:d:h:m:s]: 00:258:12:53:23
Block: 1071644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184702 RingCT/type: yes/0
Extra: 0160f0a12b65467798c0225b500bfddd9fbac3635e1f819b6172b3930655e749d602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf6e3023bcca3d2863f6bd861a0b16a3aecc286b97b81db633e0bbbf936f7131 0.600000000000 1543947 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": 1071654, "vin": [ { "gen": { "height": 1071644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf6e3023bcca3d2863f6bd861a0b16a3aecc286b97b81db633e0bbbf936f7131" } } ], "extra": [ 1, 96, 240, 161, 43, 101, 70, 119, 152, 192, 34, 91, 80, 11, 253, 221, 159, 186, 195, 99, 94, 31, 129, 155, 97, 114, 179, 147, 6, 85, 231, 73, 214, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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