Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405bf64f6a49fbea0571ee6239f909af60d986c3c2c811d8de24f514d0ebefad

Tx prefix hash: cca1ccecb9a6e7ca209130e28f69d850cdd9490a9023b0c9e57b9971d69973fb
Tx public key: 40a716ed4e2e6663523edd30e1d3a2e8091ba20820ef4f0207aeb89f63bc7587
Timestamp: 1676463173 Timestamp [UCT]: 2023-02-15 12:12:53 Age [y:d:h:m:s]: 02:054:02:32:47
Block: 697500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560267 RingCT/type: yes/0
Extra: 0140a716ed4e2e6663523edd30e1d3a2e8091ba20820ef4f0207aeb89f63bc7587021100000016835e4d22000000000000000000

1 output(s) for total of 2.998422795000 dcy

stealth address amount amount idx
00: b0483fadc83f0e70f3ddc3e37294a022ba2bba98403bef7fcaa06621f5dda715 2.998422795000 1140701 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": 697510, "vin": [ { "gen": { "height": 697500 } } ], "vout": [ { "amount": 2998422795, "target": { "key": "b0483fadc83f0e70f3ddc3e37294a022ba2bba98403bef7fcaa06621f5dda715" } } ], "extra": [ 1, 64, 167, 22, 237, 78, 46, 102, 99, 82, 62, 221, 48, 225, 211, 162, 232, 9, 27, 162, 8, 32, 239, 79, 2, 7, 174, 184, 159, 99, 188, 117, 135, 2, 17, 0, 0, 0, 22, 131, 94, 77, 34, 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