Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef8a4ad9785a08ab9d6c0a22a732112e60daff6d8a66044b1c44f5c3c5cac93

Tx prefix hash: c2e34d094594452c670d49fa92e1d4a64f8491e1c3fc6966dab44d06c7a2006a
Tx public key: 84c0f344a58b19126a9dbd3bfd81a69bf8fea8e4f3398c3dabecab9f530ccc62
Timestamp: 1713566387 Timestamp [UCT]: 2024-04-19 22:39:47 Age [y:d:h:m:s]: 00:305:21:56:23
Block: 1004199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218673 RingCT/type: yes/0
Extra: 0184c0f344a58b19126a9dbd3bfd81a69bf8fea8e4f3398c3dabecab9f530ccc620211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e484e356e520450462afc4e1730e0b588b84d4ec5ea77c2babaf09d2629554e5 0.600000000000 1464767 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": 1004209, "vin": [ { "gen": { "height": 1004199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e484e356e520450462afc4e1730e0b588b84d4ec5ea77c2babaf09d2629554e5" } } ], "extra": [ 1, 132, 192, 243, 68, 165, 139, 25, 18, 106, 157, 189, 59, 253, 129, 166, 155, 248, 254, 168, 228, 243, 57, 140, 61, 171, 236, 171, 159, 83, 12, 204, 98, 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