Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6767f9645dd29e8041ef89aab54eb2fbc99c701a159a2e4ee1983b3d0cc246bd

Tx prefix hash: 12d97d48e8d8b2b680a68e4d6962c124ba5a4eeecda244fd264f05850291a5d4
Tx public key: df4eef3dffa8db0d8595cd5381c4ecb7bff2e37e389c79eb786ac1e565c7f7f3
Timestamp: 1583540936 Timestamp [UCT]: 2020-03-07 00:28:56 Age [y:d:h:m:s]: 04:301:01:59:59
Block: 78039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109532 RingCT/type: yes/0
Extra: 01df4eef3dffa8db0d8595cd5381c4ecb7bff2e37e389c79eb786ac1e565c7f7f30211000000324ac5aa02000000000000000000

1 output(s) for total of 338.395976202000 dcy

stealth address amount amount idx
00: 01b82cf5877ac3642b1af78f51e9cb0e5f8dacc529ef1870c17bb9e8e4d27831 338.395976202000 143296 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": 78049, "vin": [ { "gen": { "height": 78039 } } ], "vout": [ { "amount": 338395976202, "target": { "key": "01b82cf5877ac3642b1af78f51e9cb0e5f8dacc529ef1870c17bb9e8e4d27831" } } ], "extra": [ 1, 223, 78, 239, 61, 255, 168, 219, 13, 133, 149, 205, 83, 129, 196, 236, 183, 191, 242, 227, 126, 56, 156, 121, 235, 120, 106, 193, 229, 101, 199, 247, 243, 2, 17, 0, 0, 0, 50, 74, 197, 170, 2, 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