Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b013b501bb185d9dc497a5c03002dac6c80974021325575c25f09e0b3656fd4e

Tx prefix hash: 8982d92d24743d299b0fff2420d8b5966b53c3165f5ada444498e10decbd79d5
Tx public key: d3f9e5711dcfc950d381b7e522240b3215d35e2a6657d9372aec7b40646176f2
Timestamp: 1700060966 Timestamp [UCT]: 2023-11-15 15:09:26 Age [y:d:h:m:s]: 01:358:21:45:50
Block: 892256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515405 RingCT/type: yes/0
Extra: 01d3f9e5711dcfc950d381b7e522240b3215d35e2a6657d9372aec7b40646176f202110000000575e3f0e9000000000000000000

1 output(s) for total of 0.678555654000 dcy

stealth address amount amount idx
00: 2563dd0f10bb017900461b42228cfb23f05b0feb123bc4297d2c1ecb7a1ac534 0.678555654000 1348357 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": 892266, "vin": [ { "gen": { "height": 892256 } } ], "vout": [ { "amount": 678555654, "target": { "key": "2563dd0f10bb017900461b42228cfb23f05b0feb123bc4297d2c1ecb7a1ac534" } } ], "extra": [ 1, 211, 249, 229, 113, 29, 207, 201, 80, 211, 129, 183, 229, 34, 36, 11, 50, 21, 211, 94, 42, 102, 87, 217, 55, 42, 236, 123, 64, 100, 97, 118, 242, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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