Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60fb15d8ff0c11577255500e04f1e9b1f81e7283635de8771cf1829254ffc5a2

Tx prefix hash: 913f25c111255579e4e42645c0d92582c6fb1d89fa2fbcf2e35371ac3a6d3983
Tx public key: efd77f52a1d5b94dd2ba818eeff6a7356395c4aae62f2b3807f0516f50094793
Timestamp: 1753124418 Timestamp [UCT]: 2025-07-21 19:00:18 Age [y:d:h:m:s]: 00:117:21:36:52
Block: 1330428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83067 RingCT/type: yes/0
Extra: 01efd77f52a1d5b94dd2ba818eeff6a7356395c4aae62f2b3807f0516f50094793021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f66ef513cd4fd457e197362a321d5a757800ec8729c104d415b43ea3144c35ac 0.600000000000 1818219 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": 1330438, "vin": [ { "gen": { "height": 1330428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f66ef513cd4fd457e197362a321d5a757800ec8729c104d415b43ea3144c35ac" } } ], "extra": [ 1, 239, 215, 127, 82, 161, 213, 185, 77, 210, 186, 129, 142, 239, 246, 167, 53, 99, 149, 196, 170, 230, 47, 43, 56, 7, 240, 81, 111, 80, 9, 71, 147, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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