Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1176fad18eb5a1e6c63947e95899c5c31bac69febbea07ebc9ecd745b47a3c0

Tx prefix hash: 6880fa0607336d6c346b25b9a09614cb2f065d17cf8e7e42aab40e92e85b8529
Tx public key: cd38dbbb44f28ed15e1c47c88a1588cf1257482919fd5d88dec09ac250f7485e
Timestamp: 1697002669 Timestamp [UCT]: 2023-10-11 05:37:49 Age [y:d:h:m:s]: 02:030:19:07:02
Block: 867097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541634 RingCT/type: yes/0
Extra: 01cd38dbbb44f28ed15e1c47c88a1588cf1257482919fd5d88dec09ac250f7485e021100000004faf35c9c000000000000000000

1 output(s) for total of 0.822143678000 dcy

stealth address amount amount idx
00: f1602f9670d38606fe4e7cb9b89a249d049c5a6c56c33ed674589a89c6d125db 0.822143678000 1321749 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": 867107, "vin": [ { "gen": { "height": 867097 } } ], "vout": [ { "amount": 822143678, "target": { "key": "f1602f9670d38606fe4e7cb9b89a249d049c5a6c56c33ed674589a89c6d125db" } } ], "extra": [ 1, 205, 56, 219, 187, 68, 242, 142, 209, 94, 28, 71, 200, 138, 21, 136, 207, 18, 87, 72, 41, 25, 253, 93, 136, 222, 192, 154, 194, 80, 247, 72, 94, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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