Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d4227b476a66cd66cc54b0bce5adc6d4ac600a08a9615095338cf5f2ddda51

Tx prefix hash: 62615398ca8caf280f23899fa185fe0dc2d5238bba12a2b5a02542db601b09e6
Tx public key: 116b04a398c5d0a4c43a7f4e0dbb1723099d91ece94a722c93c9d737203d1da0
Timestamp: 1724750653 Timestamp [UCT]: 2024-08-27 09:24:13 Age [y:d:h:m:s]: 00:225:05:30:02
Block: 1096934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160837 RingCT/type: yes/0
Extra: 01116b04a398c5d0a4c43a7f4e0dbb1723099d91ece94a722c93c9d737203d1da0021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f5e0a66731cac5c19a7e6bc1db4d7c0f809cad3a526fe330b4ff33b9d318e3d 0.600000000000 1572169 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": 1096944, "vin": [ { "gen": { "height": 1096934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f5e0a66731cac5c19a7e6bc1db4d7c0f809cad3a526fe330b4ff33b9d318e3d" } } ], "extra": [ 1, 17, 107, 4, 163, 152, 197, 208, 164, 196, 58, 127, 78, 13, 187, 23, 35, 9, 157, 145, 236, 233, 74, 114, 44, 147, 201, 215, 55, 32, 61, 29, 160, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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