Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe99e766dcd7055b0eb3633bb388447b8e4ffd86cee5c6f39b2e3140ee40c94b

Tx prefix hash: ba141ec8b27a72d4c0c2051a80630f9cc16a02eaac4062dfc572d1e752efdfc4
Tx public key: 7bb4eebf74d739cd1a26da3154854c81e6c1c5eaac6a2740400e9dc7222d6a7f
Timestamp: 1755676242 Timestamp [UCT]: 2025-08-20 07:50:42 Age [y:d:h:m:s]: 00:131:03:40:17
Block: 1350437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93698 RingCT/type: yes/0
Extra: 017bb4eebf74d739cd1a26da3154854c81e6c1c5eaac6a2740400e9dc7222d6a7f021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66a4f3b4ed474144f79bec9982ffdfa108a834c87619857c9bc50deab7b8b782 0.600000000000 1838382 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": 1350447, "vin": [ { "gen": { "height": 1350437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66a4f3b4ed474144f79bec9982ffdfa108a834c87619857c9bc50deab7b8b782" } } ], "extra": [ 1, 123, 180, 238, 191, 116, 215, 57, 205, 26, 38, 218, 49, 84, 133, 76, 129, 230, 193, 197, 234, 172, 106, 39, 64, 64, 14, 157, 199, 34, 45, 106, 127, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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