Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1589b3c52beb712a1bd1761fe591c635d90eeede723f91510d36191eefb07855

Tx prefix hash: c49060c6fd90d2fbbef78d34bb0d84158d26af8b4be00aa9df7ba4c28d91fccb
Tx public key: 7931a3d070c962d6528f26aa226ff5bda90f7603671ebfd65faf11c8c9ee982e
Timestamp: 1707718143 Timestamp [UCT]: 2024-02-12 06:09:03 Age [y:d:h:m:s]: 00:314:13:53:04
Block: 955725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225255 RingCT/type: yes/0
Extra: 017931a3d070c962d6528f26aa226ff5bda90f7603671ebfd65faf11c8c9ee982e0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37ded36e50962b2a1d944ce21770d55dc9342ddb1905d1767a9e50201932c14d 0.600000000000 1415023 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": 955735, "vin": [ { "gen": { "height": 955725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37ded36e50962b2a1d944ce21770d55dc9342ddb1905d1767a9e50201932c14d" } } ], "extra": [ 1, 121, 49, 163, 208, 112, 201, 98, 214, 82, 143, 38, 170, 34, 111, 245, 189, 169, 15, 118, 3, 103, 30, 191, 214, 95, 175, 17, 200, 201, 238, 152, 46, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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