Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80019052d7492d554f98aa29d5d5c16af74b3cd46dc41aa9db735e01807ac023

Tx prefix hash: 5d4d8aa397f7aa785592f714d4e45648f1bfcd9065a924e56958666203d0b390
Tx public key: 4ebab31ed4d4eb62bfe49c4726566c68dca2dbf3a66d8850a0461f23d0bee98b
Timestamp: 1707764288 Timestamp [UCT]: 2024-02-12 18:58:08 Age [y:d:h:m:s]: 01:126:15:53:44
Block: 956108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351501 RingCT/type: yes/0
Extra: 014ebab31ed4d4eb62bfe49c4726566c68dca2dbf3a66d8850a0461f23d0bee98b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e6c77fe8b29cf5e7549c060d0c9255cb2067031d45216b3cfd9c302b157c21 0.600000000000 1415410 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": 956118, "vin": [ { "gen": { "height": 956108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e6c77fe8b29cf5e7549c060d0c9255cb2067031d45216b3cfd9c302b157c21" } } ], "extra": [ 1, 78, 186, 179, 30, 212, 212, 235, 98, 191, 228, 156, 71, 38, 86, 108, 104, 220, 162, 219, 243, 166, 109, 136, 80, 160, 70, 31, 35, 208, 190, 233, 139, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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