Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1595e0c10b3c5cc13f68ed4cfea75b6e008c86cb4cd121a854b01363bb3935c

Tx prefix hash: 868380fa780174e0a8584ba51139711bc1660a5b1a926a2c991f55b3aad0e3cb
Tx public key: 387258f7463fc301fb1989939c0198d1a9d5437889b55f90d1c4d3b2cb5fe54e
Timestamp: 1636802604 Timestamp [UCT]: 2021-11-13 11:23:24 Age [y:d:h:m:s]: 03:330:15:20:26
Block: 373486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1012388 RingCT/type: yes/0
Extra: 01387258f7463fc301fb1989939c0198d1a9d5437889b55f90d1c4d3b2cb5fe54e021100000007f79c6ccf000000000000000000

1 output(s) for total of 35.521085559000 dcy

stealth address amount amount idx
00: f1e9dd5248762457b8b3d74b9145bdfa9d10c7e4e1a9f8e51f867b5437901f47 35.521085559000 756260 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": 373496, "vin": [ { "gen": { "height": 373486 } } ], "vout": [ { "amount": 35521085559, "target": { "key": "f1e9dd5248762457b8b3d74b9145bdfa9d10c7e4e1a9f8e51f867b5437901f47" } } ], "extra": [ 1, 56, 114, 88, 247, 70, 63, 195, 1, 251, 25, 137, 147, 156, 1, 152, 209, 169, 213, 67, 120, 137, 181, 95, 144, 209, 196, 211, 178, 203, 95, 229, 78, 2, 17, 0, 0, 0, 7, 247, 156, 108, 207, 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