Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a5a0389c76480c38ad6906a246de700ea15eb7c386a7d86837f3e1cf3fb38c

Tx prefix hash: f12c86e34acf9e8e110536606e301aa30de863064ea986ec37dc6b9e4d63e0fe
Tx public key: 400e3147fde1a4c86758c789b6d02e4a3e3761932a44028ec9dfe3b7032ec636
Timestamp: 1715442266 Timestamp [UCT]: 2024-05-11 15:44:26 Age [y:d:h:m:s]: 00:289:15:30:35
Block: 1019792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206980 RingCT/type: yes/0
Extra: 01400e3147fde1a4c86758c789b6d02e4a3e3761932a44028ec9dfe3b7032ec6360211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ff7e90e3d58adc6776a738532af601585e826fd607c7ab22af8164bea3ddb43 0.600000000000 1483833 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": 1019802, "vin": [ { "gen": { "height": 1019792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ff7e90e3d58adc6776a738532af601585e826fd607c7ab22af8164bea3ddb43" } } ], "extra": [ 1, 64, 14, 49, 71, 253, 225, 164, 200, 103, 88, 199, 137, 182, 208, 46, 74, 62, 55, 97, 147, 42, 68, 2, 142, 201, 223, 227, 183, 3, 46, 198, 54, 2, 17, 0, 0, 0, 7, 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