Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9223f6a051d39d08e08466f28f10d07d8afb846610754857eca8b06bc19e973

Tx prefix hash: c195de53fd6d27aaf6760d99c0b176f61968f1e372b451d9954d534d368f5236
Tx public key: b5d988eb62cb0399a5dc267b824ce05af6e8293b92127454e8a61a2c7654b6c6
Timestamp: 1738285939 Timestamp [UCT]: 2025-01-31 01:12:19 Age [y:d:h:m:s]: 00:139:02:43:15
Block: 1208728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99360 RingCT/type: yes/0
Extra: 01b5d988eb62cb0399a5dc267b824ce05af6e8293b92127454e8a61a2c7654b6c6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2571a4c78c3c8ec4f583d808e61b0a354498fb9e741288b8ef09203d96d365db 0.600000000000 1695463 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": 1208738, "vin": [ { "gen": { "height": 1208728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2571a4c78c3c8ec4f583d808e61b0a354498fb9e741288b8ef09203d96d365db" } } ], "extra": [ 1, 181, 217, 136, 235, 98, 203, 3, 153, 165, 220, 38, 123, 130, 76, 224, 90, 246, 232, 41, 59, 146, 18, 116, 84, 232, 166, 26, 44, 118, 84, 182, 198, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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