Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a85b08cb3d14c860d85c8bd0e62fb248ead3485b89f45490de50debd9b539f42

Tx prefix hash: 5da15527a2b2eabbd70e00cf9674533402d65ed9adf5edf4f367538c68d7df72
Tx public key: 2587b28fb202c8475372deba5d9e760a00d7b5c2174c3d1e0b982e4e345cd497
Timestamp: 1726463262 Timestamp [UCT]: 2024-09-16 05:07:42 Age [y:d:h:m:s]: 00:073:05:26:13
Block: 1111135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52359 RingCT/type: yes/0
Extra: 012587b28fb202c8475372deba5d9e760a00d7b5c2174c3d1e0b982e4e345cd49702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5b9eb22eb4799add6991c2d84ddbeac6ef770d59e95ae3734fa85a72650fea8 0.600000000000 1589990 of 15

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": 1111145, "vin": [ { "gen": { "height": 1111135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5b9eb22eb4799add6991c2d84ddbeac6ef770d59e95ae3734fa85a72650fea8" } } ], "extra": [ 1, 37, 135, 178, 143, 178, 2, 200, 71, 83, 114, 222, 186, 93, 158, 118, 10, 0, 215, 181, 194, 23, 76, 61, 30, 11, 152, 46, 78, 52, 92, 212, 151, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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