Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde6e969b3becd6ae3a06c237868a36bb08d27067b6a1a39b49ac17ed505f75b

Tx prefix hash: 1e3b5a2285e821e2992fe06ea30c6a688e5387d6fb7ec13a5a7d915955f960e1
Tx public key: d8ab0c69b0e419b71d79e4879b530097e8f3b17c02056280d07c08221f73d80f
Timestamp: 1703877795 Timestamp [UCT]: 2023-12-29 19:23:15 Age [y:d:h:m:s]: 01:104:07:23:51
Block: 923890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335670 RingCT/type: yes/0
Extra: 01d8ab0c69b0e419b71d79e4879b530097e8f3b17c02056280d07c08221f73d80f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2d178cd6f5f2ab6d63108298387b10eb8d8f4ce2c1b316cf74a9d8c4b38f77d 0.600000000000 1381628 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": 923900, "vin": [ { "gen": { "height": 923890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2d178cd6f5f2ab6d63108298387b10eb8d8f4ce2c1b316cf74a9d8c4b38f77d" } } ], "extra": [ 1, 216, 171, 12, 105, 176, 228, 25, 183, 29, 121, 228, 135, 155, 83, 0, 151, 232, 243, 177, 124, 2, 5, 98, 128, 208, 124, 8, 34, 31, 115, 216, 15, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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