Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db024cbdb0e0555d014283054073e6fb5b6ed2d4dd0d1960cc2f56224b19b7a9

Tx prefix hash: 7f9f8e9dc5e0fa82c34f9aa45cae50acaf7465c5697f6a4782cde074b5aee38d
Tx public key: 05216479edb9b40ae4dbb9ebaea7e15d7640639cf03b3d396a6a262441956ad5
Timestamp: 1704542441 Timestamp [UCT]: 2024-01-06 12:00:41 Age [y:d:h:m:s]: 01:333:14:10:36
Block: 929380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497303 RingCT/type: yes/0
Extra: 0105216479edb9b40ae4dbb9ebaea7e15d7640639cf03b3d396a6a262441956ad502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e47f16b76bb306ce3800fdbe8eab4eaeb6740e5f9a31c469c7abb2cff6ab7a3c 0.600000000000 1387252 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": 929390, "vin": [ { "gen": { "height": 929380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e47f16b76bb306ce3800fdbe8eab4eaeb6740e5f9a31c469c7abb2cff6ab7a3c" } } ], "extra": [ 1, 5, 33, 100, 121, 237, 185, 180, 10, 228, 219, 185, 235, 174, 167, 225, 93, 118, 64, 99, 156, 240, 59, 61, 57, 106, 106, 38, 36, 65, 149, 106, 213, 2, 17, 0, 0, 0, 2, 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