Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa9293095fb25075a44a1f3fd43e899dd51472cbc40f5bd625732f911df8ac4d

Tx prefix hash: 40821db09cd840d073bfa0d96b730268f4b6c4ca1695e2e3c4544779271925ba
Tx public key: b7993d6de6036df17b87bfcb4e0f1e56efb811fb5728f42285f8251c04e43d26
Timestamp: 1584904426 Timestamp [UCT]: 2020-03-22 19:13:46 Age [y:d:h:m:s]: 04:280:09:30:48
Block: 86593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097476 RingCT/type: yes/0
Extra: 01b7993d6de6036df17b87bfcb4e0f1e56efb811fb5728f42285f8251c04e43d26021100000002d81c26c0000000000000000000

1 output(s) for total of 317.016761296000 dcy

stealth address amount amount idx
00: c5f26cda434fd8604fc5ce93fb8b4ba204c4b5954201b3ac1dfb9126e8394dee 317.016761296000 156241 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": 86603, "vin": [ { "gen": { "height": 86593 } } ], "vout": [ { "amount": 317016761296, "target": { "key": "c5f26cda434fd8604fc5ce93fb8b4ba204c4b5954201b3ac1dfb9126e8394dee" } } ], "extra": [ 1, 183, 153, 61, 109, 230, 3, 109, 241, 123, 135, 191, 203, 78, 15, 30, 86, 239, 184, 17, 251, 87, 40, 244, 34, 133, 248, 37, 28, 4, 228, 61, 38, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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