Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0cf0ee05099e235bedc0ef034f1483a0a9222736d3d7c880fef5dca98fd8b81

Tx prefix hash: 025367d0230b51ca09b178b0e4c7d956f88b53711aebd44c6956926d1a6705d0
Tx public key: eb7458000009e4b1ecf674374d418ff78fe82f810dd493f2a7f869e2e3c3af7e
Timestamp: 1635058880 Timestamp [UCT]: 2021-10-24 07:01:20 Age [y:d:h:m:s]: 03:026:12:15:56
Block: 359346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 797238 RingCT/type: yes/0
Extra: 01eb7458000009e4b1ecf674374d418ff78fe82f810dd493f2a7f869e2e3c3af7e0211000000034a0f5013000000000000000000

1 output(s) for total of 39.568998889000 dcy

stealth address amount amount idx
00: 2fa2758164506d3683fed7995bc55dadf79580f98f4f0c8cdcb262392bd33104 39.568998889000 731799 of 0

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": 359356, "vin": [ { "gen": { "height": 359346 } } ], "vout": [ { "amount": 39568998889, "target": { "key": "2fa2758164506d3683fed7995bc55dadf79580f98f4f0c8cdcb262392bd33104" } } ], "extra": [ 1, 235, 116, 88, 0, 0, 9, 228, 177, 236, 246, 116, 55, 77, 65, 143, 247, 143, 232, 47, 129, 13, 212, 147, 242, 167, 248, 105, 226, 227, 195, 175, 126, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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