Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a40b4d344c0bea2c3b5731b2469e35e0b48a7b68f384e16d8efd14490edd75d1

Tx prefix hash: cda10ac3a9497330028357c32033c7c15c5e5320fb176067725bf2178e3390b4
Tx public key: 0ed853cae31e902a5a41fe126901a2922ce1a5bb74d02df90dc38d0599b468d0
Timestamp: 1716558969 Timestamp [UCT]: 2024-05-24 13:56:09 Age [y:d:h:m:s]: 00:335:18:46:23
Block: 1029037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239997 RingCT/type: yes/0
Extra: 010ed853cae31e902a5a41fe126901a2922ce1a5bb74d02df90dc38d0599b468d002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eb1eeb0df7d8231826d39319ec1fb40ee5c4919e6b161e553cff1d31f5482f4 0.600000000000 1497038 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": 1029047, "vin": [ { "gen": { "height": 1029037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eb1eeb0df7d8231826d39319ec1fb40ee5c4919e6b161e553cff1d31f5482f4" } } ], "extra": [ 1, 14, 216, 83, 202, 227, 30, 144, 42, 90, 65, 254, 18, 105, 1, 162, 146, 44, 225, 165, 187, 116, 208, 45, 249, 13, 195, 141, 5, 153, 180, 104, 208, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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