Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b533518aecbddcc0d72cad68e4fb37f97ef9410fde1ac0c9410589098bd84ca

Tx prefix hash: 39c8f595925548591a45a89ac21d9a99549d90a729c4aac5e7ad0494d39f4140
Tx public key: ebd5656fb172fdc604a3610cc89edfbe6d4b368b700b165249c18c2cdb1c84db
Timestamp: 1638807654 Timestamp [UCT]: 2021-12-06 16:20:54 Age [y:d:h:m:s]: 03:099:02:47:12
Block: 389769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 849553 RingCT/type: yes/0
Extra: 01ebd5656fb172fdc604a3610cc89edfbe6d4b368b700b165249c18c2cdb1c84db021100000001b09bf7ff000000000000000000

1 output(s) for total of 31.371397716000 dcy

stealth address amount amount idx
00: 835d3cbfe2e3a996227c6b6feb9821a3466dd2e7e9c28ecff6c981c0c2183a28 31.371397716000 785130 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": 389779, "vin": [ { "gen": { "height": 389769 } } ], "vout": [ { "amount": 31371397716, "target": { "key": "835d3cbfe2e3a996227c6b6feb9821a3466dd2e7e9c28ecff6c981c0c2183a28" } } ], "extra": [ 1, 235, 213, 101, 111, 177, 114, 253, 198, 4, 163, 97, 12, 200, 158, 223, 190, 109, 75, 54, 139, 112, 11, 22, 82, 73, 193, 140, 44, 219, 28, 132, 219, 2, 17, 0, 0, 0, 1, 176, 155, 247, 255, 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