Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 468677ca1254ec84c1fd99e29db48c0cb10126c040c3c4679bd7fec752d5fd35

Tx prefix hash: 3def913fe2f46d71780a74ac58dabf14ffc9c6a09b83cf95e1b7ff8b31dbd440
Tx public key: 824942492fac64f47d6a04009d36c2a51fc807fca96dd32bbf308b16f455c5cb
Timestamp: 1764223632 Timestamp [UCT]: 2025-11-27 06:07:12 Age [y:d:h:m:s]: 00:010:03:49:02
Block: 1421061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7275 RingCT/type: yes/0
Extra: 01824942492fac64f47d6a04009d36c2a51fc807fca96dd32bbf308b16f455c5cb021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f493f7d0b2606a2d32605227ba889410794be15fd15b5f87c3a89278bc78da64 0.600000000000 1909616 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": 1421071, "vin": [ { "gen": { "height": 1421061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f493f7d0b2606a2d32605227ba889410794be15fd15b5f87c3a89278bc78da64" } } ], "extra": [ 1, 130, 73, 66, 73, 47, 172, 100, 244, 125, 106, 4, 0, 157, 54, 194, 165, 31, 200, 7, 252, 169, 109, 211, 43, 191, 48, 139, 22, 244, 85, 197, 203, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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