Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8823e02b4de87f94a75ffe84ff1f249fb9c0eb5604ec4bfd72a45e9ed33fa342

Tx prefix hash: 605cb2deba155721b5e3849dfaca03859fdf776d8e9d183e69d9a3fc5dcb128c
Tx public key: 0e15bd321239eeb70e4d69a700b2dcfbf5b31d1bd0da19c9d6308266dcf5815d
Timestamp: 1736724304 Timestamp [UCT]: 2025-01-12 23:25:04 Age [y:d:h:m:s]: 00:312:04:35:36
Block: 1196058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220632 RingCT/type: yes/0
Extra: 010e15bd321239eeb70e4d69a700b2dcfbf5b31d1bd0da19c9d6308266dcf5815d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a482e90dcfe89efd32ef7a297837b62f461650b9069c37e774cabfa3b32639ba 0.600000000000 1682655 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": 1196068, "vin": [ { "gen": { "height": 1196058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a482e90dcfe89efd32ef7a297837b62f461650b9069c37e774cabfa3b32639ba" } } ], "extra": [ 1, 14, 21, 189, 50, 18, 57, 238, 183, 14, 77, 105, 167, 0, 178, 220, 251, 245, 179, 29, 27, 208, 218, 25, 201, 214, 48, 130, 102, 220, 245, 129, 93, 2, 17, 0, 0, 0, 4, 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