Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a0d066c8df9d1ce8eefe80a1f2ff8fe0afaa8099814669255c7f60108809170

Tx prefix hash: 0a1e64f07c736c154a31a2c411a5fa6d961c24b8f37cb54a86b8e52c569594af
Tx public key: 5b946777dceacb7b6574233741e7e53a5c27ecba311724339d6a5b41dc3d6b6b
Timestamp: 1765913855 Timestamp [UCT]: 2025-12-16 19:37:35 Age [y:d:h:m:s]: 00:006:17:12:22
Block: 1435060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4805 RingCT/type: yes/0
Extra: 015b946777dceacb7b6574233741e7e53a5c27ecba311724339d6a5b41dc3d6b6b02110000000970609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05805ca25f6dec4cc4ff050816044f1fa8bd36b2ba505c25c338528ed6d98276 0.600000000000 1923857 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": 1435070, "vin": [ { "gen": { "height": 1435060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05805ca25f6dec4cc4ff050816044f1fa8bd36b2ba505c25c338528ed6d98276" } } ], "extra": [ 1, 91, 148, 103, 119, 220, 234, 203, 123, 101, 116, 35, 55, 65, 231, 229, 58, 92, 39, 236, 186, 49, 23, 36, 51, 157, 106, 91, 65, 220, 61, 107, 107, 2, 17, 0, 0, 0, 9, 112, 96, 157, 3, 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