Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebaf881aad99954eacd4f3723780d4b0bbf6b7a9cfa979c2fac810d39482df0c

Tx prefix hash: da7caa0e598f3dd0715fe6039cafd2d342f329093e76df13e6854220db9016d5
Tx public key: 6c9ad23a5a12119eb91c466605099d5417e6345b6ae2a5cf494494735c0d0beb
Timestamp: 1716079107 Timestamp [UCT]: 2024-05-19 00:38:27 Age [y:d:h:m:s]: 01:218:14:18:39
Block: 1025049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414882 RingCT/type: yes/0
Extra: 016c9ad23a5a12119eb91c466605099d5417e6345b6ae2a5cf494494735c0d0beb02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d4bdb5a7602e48fb2bc8bfd90a7ccd2c87273f7ac4b387151b0c303b5468947 0.600000000000 1491268 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": 1025059, "vin": [ { "gen": { "height": 1025049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d4bdb5a7602e48fb2bc8bfd90a7ccd2c87273f7ac4b387151b0c303b5468947" } } ], "extra": [ 1, 108, 154, 210, 58, 90, 18, 17, 158, 185, 28, 70, 102, 5, 9, 157, 84, 23, 230, 52, 91, 106, 226, 165, 207, 73, 68, 148, 115, 92, 13, 11, 235, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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