Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9582e9c60ac883b57a0ef2505e2dba823c12ad0211614c8d92ed138fd5abe28b

Tx prefix hash: 5563d8b0634ae807efd433ecad4e6e340613b501c55a416f105851ad0f7991a3
Tx public key: 0cdb17421bb4fc1e746f7e60622cae71a01cd9ce151cd7ca3b1c1fb141c62e0a
Timestamp: 1703155758 Timestamp [UCT]: 2023-12-21 10:49:18 Age [y:d:h:m:s]: 01:144:01:48:14
Block: 917909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364112 RingCT/type: yes/0
Extra: 010cdb17421bb4fc1e746f7e60622cae71a01cd9ce151cd7ca3b1c1fb141c62e0a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da1159fa909cff0a602b24efa2ee29653dee4affd5b487789615564d1cf5c21b 0.600000000000 1375533 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": 917919, "vin": [ { "gen": { "height": 917909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da1159fa909cff0a602b24efa2ee29653dee4affd5b487789615564d1cf5c21b" } } ], "extra": [ 1, 12, 219, 23, 66, 27, 180, 252, 30, 116, 111, 126, 96, 98, 44, 174, 113, 160, 28, 217, 206, 21, 28, 215, 202, 59, 28, 31, 177, 65, 198, 46, 10, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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