Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d04c49f4c8ef7b7430b7e032e0a7ee1512d632c333f72996a894715954b200a9

Tx prefix hash: 48fe004d1ab4c9f7baae4434dd3590a43005ba1493a8b366ba411e1efd32320e
Tx public key: db4fff0a74a04b8f9c303b94624f7eb93ae78846781bcaf2c50fc32d72ebd854
Timestamp: 1734643663 Timestamp [UCT]: 2024-12-19 21:27:43 Age [y:d:h:m:s]: 00:095:11:57:54
Block: 1178861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68017 RingCT/type: yes/0
Extra: 01db4fff0a74a04b8f9c303b94624f7eb93ae78846781bcaf2c50fc32d72ebd85402110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 438ccac0a460cb4ebdc6e5d009bdbe70bda200c04aa64a3ca00047de40129f09 0.600000000000 1665250 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": 1178871, "vin": [ { "gen": { "height": 1178861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "438ccac0a460cb4ebdc6e5d009bdbe70bda200c04aa64a3ca00047de40129f09" } } ], "extra": [ 1, 219, 79, 255, 10, 116, 160, 75, 143, 156, 48, 59, 148, 98, 79, 126, 185, 58, 231, 136, 70, 120, 27, 202, 242, 197, 15, 195, 45, 114, 235, 216, 84, 2, 17, 0, 0, 0, 10, 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