Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f0fbffb14c24434e8015ba25d180a299105ef2c4e910a9bb9c919695d7f764

Tx prefix hash: 22a378b9a0e4861fcc477c7175d33b3840e821dd5e65712f0a719b4cffff8d1e
Tx public key: 8359fca172a34c5abcbf1e3e7895473c9ca69cd6aec83eecd720c692714ce338
Timestamp: 1745501627 Timestamp [UCT]: 2025-04-24 13:33:47 Age [y:d:h:m:s]: 00:013:12:40:51
Block: 1268463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9677 RingCT/type: yes/0
Extra: 018359fca172a34c5abcbf1e3e7895473c9ca69cd6aec83eecd720c692714ce3380211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493d435f5c421e081fe9d50bb024f5259b3db9efd0b6a36749e860d79c7c0902 0.600000000000 1755692 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": 1268473, "vin": [ { "gen": { "height": 1268463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493d435f5c421e081fe9d50bb024f5259b3db9efd0b6a36749e860d79c7c0902" } } ], "extra": [ 1, 131, 89, 252, 161, 114, 163, 76, 90, 188, 191, 30, 62, 120, 149, 71, 60, 156, 166, 156, 214, 174, 200, 62, 236, 215, 32, 198, 146, 113, 76, 227, 56, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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