Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cef0e7962c83c42a950c87263bd29ff0b33f45135b9b0d5fccd8cbf0cea8f17f

Tx prefix hash: daa6dc2dfcc21bfb42f3cb9054c4deef4b591f3449dfeee67c33c3f00e5a6a13
Tx public key: d372f73a36dc276a3e84fe08032099fa4b88f2cef875b1254d46e3914d3bd529
Timestamp: 1722359436 Timestamp [UCT]: 2024-07-30 17:10:36 Age [y:d:h:m:s]: 00:234:03:09:02
Block: 1077106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167244 RingCT/type: yes/0
Extra: 01d372f73a36dc276a3e84fe08032099fa4b88f2cef875b1254d46e3914d3bd529021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad161f49e3db4f0e2d3d029019df59d5d1bcf3849bd3ee92e794b956d46d30e1 0.600000000000 1549651 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": 1077116, "vin": [ { "gen": { "height": 1077106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad161f49e3db4f0e2d3d029019df59d5d1bcf3849bd3ee92e794b956d46d30e1" } } ], "extra": [ 1, 211, 114, 247, 58, 54, 220, 39, 106, 62, 132, 254, 8, 3, 32, 153, 250, 75, 136, 242, 206, 248, 117, 177, 37, 77, 70, 227, 145, 77, 59, 213, 41, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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