Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b6dcd3b3084e331efd38fb1d56798c17c5792d5eacdb54615048698700a07c

Tx prefix hash: a5c9537fb1918bed0de6b6ffc3bb04ff7a1137a4d5d4e88292daf808a8101f24
Tx public key: 9bea91d046258c00ee6a8c8e1e63e0654b01bf5cf59117b1e70c51bad4f25952
Timestamp: 1583528794 Timestamp [UCT]: 2020-03-06 21:06:34 Age [y:d:h:m:s]: 05:070:01:46:59
Block: 77584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205468 RingCT/type: yes/0
Extra: 019bea91d046258c00ee6a8c8e1e63e0654b01bf5cf59117b1e70c51bad4f259520211000000094943cd9f000000000000000000

1 output(s) for total of 339.572721137000 dcy

stealth address amount amount idx
00: bea65588a8cfd0ffe844dc8a403c11f9f5f20cf105203609687955672466ee48 339.572721137000 142725 of 0

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": 77594, "vin": [ { "gen": { "height": 77584 } } ], "vout": [ { "amount": 339572721137, "target": { "key": "bea65588a8cfd0ffe844dc8a403c11f9f5f20cf105203609687955672466ee48" } } ], "extra": [ 1, 155, 234, 145, 208, 70, 37, 140, 0, 238, 106, 140, 142, 30, 99, 224, 101, 75, 1, 191, 92, 245, 145, 23, 177, 231, 12, 81, 186, 212, 242, 89, 82, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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