Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3ae2989093880f84bdbbcdfde8bc3c7379de4f68fb1eccb62e5c1efbdde0ed

Tx prefix hash: 543126fab681fff3efa517295b0dd956da944e860f9f92c70c50b8e26cb16e05
Tx public key: bf182225f976eca32b4df846c95acd743e1e248c9b422c75ee9de6e606356717
Timestamp: 1719429358 Timestamp [UCT]: 2024-06-26 19:15:58 Age [y:d:h:m:s]: 01:184:03:02:20
Block: 1052821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390209 RingCT/type: yes/0
Extra: 01bf182225f976eca32b4df846c95acd743e1e248c9b422c75ee9de6e606356717021100000002067b4ef3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f05daf26c8d2f43aeeadeda013946962067a0d31588f0aeabcbfab5daa3921d 0.600000000000 1523154 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": 1052831, "vin": [ { "gen": { "height": 1052821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f05daf26c8d2f43aeeadeda013946962067a0d31588f0aeabcbfab5daa3921d" } } ], "extra": [ 1, 191, 24, 34, 37, 249, 118, 236, 163, 43, 77, 248, 70, 201, 90, 205, 116, 62, 30, 36, 140, 155, 66, 44, 117, 238, 157, 230, 230, 6, 53, 103, 23, 2, 17, 0, 0, 0, 2, 6, 123, 78, 243, 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