Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7bc03809e0fa62848c9850c386eb093423a353f86515f904adda7e43cf55c47

Tx prefix hash: 40a57ed09637d69c47529ccde6b724633ac095e69b61a893e31580fbd35498c3
Tx public key: d4aac3e9914a2f27d4f5ba9d23b255c8ef7acc300032d1df8a127eb2ed810a93
Timestamp: 1583856526 Timestamp [UCT]: 2020-03-10 16:08:46 Age [y:d:h:m:s]: 04:253:07:01:10
Block: 79936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076064 RingCT/type: yes/0
Extra: 01d4aac3e9914a2f27d4f5ba9d23b255c8ef7acc300032d1df8a127eb2ed810a9302110000001478e4872e000000000000000000

1 output(s) for total of 333.533636843000 dcy

stealth address amount amount idx
00: 4d1a646684cb42678fa33ac121cca6f5704177762babf83fbcb7e533c6a39292 333.533636843000 146260 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": 79946, "vin": [ { "gen": { "height": 79936 } } ], "vout": [ { "amount": 333533636843, "target": { "key": "4d1a646684cb42678fa33ac121cca6f5704177762babf83fbcb7e533c6a39292" } } ], "extra": [ 1, 212, 170, 195, 233, 145, 74, 47, 39, 212, 245, 186, 157, 35, 178, 85, 200, 239, 122, 204, 48, 0, 50, 209, 223, 138, 18, 126, 178, 237, 129, 10, 147, 2, 17, 0, 0, 0, 20, 120, 228, 135, 46, 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