Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b201f9a37561ae2053eec57ff785ee7dd6c5929fa5924e866064488736c33c

Tx prefix hash: 42678d694b756f345772da3c714f02046a6d8049e6ed5cf3579b4e6a915c29f6
Tx public key: 87b184a7ef63086b404b1e9fe143be6c17966f7543562410cc6917e7e28af75f
Timestamp: 1581515641 Timestamp [UCT]: 2020-02-12 13:54:01 Age [y:d:h:m:s]: 04:282:11:00:37
Block: 63501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093982 RingCT/type: yes/0
Extra: 0187b184a7ef63086b404b1e9fe143be6c17966f7543562410cc6917e7e28af75f02110000000103d36d11000000000000000000

1 output(s) for total of 378.090390636000 dcy

stealth address amount amount idx
00: 5ccc160d95d2b5204b4baa22eb7b5c321d545c782584e2a021a14fdcf84fe852 378.090390636000 117063 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": 63511, "vin": [ { "gen": { "height": 63501 } } ], "vout": [ { "amount": 378090390636, "target": { "key": "5ccc160d95d2b5204b4baa22eb7b5c321d545c782584e2a021a14fdcf84fe852" } } ], "extra": [ 1, 135, 177, 132, 167, 239, 99, 8, 107, 64, 75, 30, 159, 225, 67, 190, 108, 23, 150, 111, 117, 67, 86, 36, 16, 204, 105, 23, 231, 226, 138, 247, 95, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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