Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61c8304f5e7c94484692ae887dad4b91a8e9b2d8a81038db855585320e3cedb

Tx prefix hash: 42afa03ae3fa22bb2b41e4ddf340d7dd360bf5f2a501659aabbf9debc1fee686
Tx public key: d9a53653b420a3f0f454c8d2c1f757a7473082b7b28dc01ce9236f02e066243c
Timestamp: 1718015117 Timestamp [UCT]: 2024-06-10 10:25:17 Age [y:d:h:m:s]: 01:007:15:55:32
Block: 1041101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266254 RingCT/type: yes/0
Extra: 01d9a53653b420a3f0f454c8d2c1f757a7473082b7b28dc01ce9236f02e066243c021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f681f35ad77fdbdcb9ea99bc7cebf925bac379124d0aa92c3ec2006be333c83d 0.600000000000 1509766 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": 1041111, "vin": [ { "gen": { "height": 1041101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f681f35ad77fdbdcb9ea99bc7cebf925bac379124d0aa92c3ec2006be333c83d" } } ], "extra": [ 1, 217, 165, 54, 83, 180, 32, 163, 240, 244, 84, 200, 210, 193, 247, 87, 167, 71, 48, 130, 183, 178, 141, 192, 28, 233, 35, 111, 2, 224, 102, 36, 60, 2, 17, 0, 0, 0, 1, 215, 73, 245, 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