Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3606b9f4a79d45d91a42704868831d7fb410565c53c02fa494729d7992e58dd

Tx prefix hash: 742f0c9861da5a79c8fc4a4d960e590c1fd357574b34a2c99b63afdbd33da226
Tx public key: 884b4708cb1a9a0a8c12faff72df5287f7e9c058d79d6709a74ec61ec4aa1479
Timestamp: 1763540246 Timestamp [UCT]: 2025-11-19 08:17:26 Age [y:d:h:m:s]: 00:008:22:05:04
Block: 1415393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6393 RingCT/type: yes/0
Extra: 01884b4708cb1a9a0a8c12faff72df5287f7e9c058d79d6709a74ec61ec4aa14790211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4f50b4a247bdb51e3fcb39c7e89a1ff5a3ad088b7337239c85f1bb42aa101e2 0.600000000000 1903894 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": 1415403, "vin": [ { "gen": { "height": 1415393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4f50b4a247bdb51e3fcb39c7e89a1ff5a3ad088b7337239c85f1bb42aa101e2" } } ], "extra": [ 1, 136, 75, 71, 8, 203, 26, 154, 10, 140, 18, 250, 255, 114, 223, 82, 135, 247, 233, 192, 88, 215, 157, 103, 9, 167, 78, 198, 30, 196, 170, 20, 121, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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