Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540ba43c90ba14bdfa1e7d9b6f1af97dc15f626d44af38688227977ce528df6b

Tx prefix hash: 663ffa5ae49e91d7a4ffc8f47a63b3ab3cb68ce98bf3ae99e2931a2f63a08cb3
Tx public key: 2be97e94fa1f9b710d74f3266262dd545f472d76ccfc2e89e55035f143dcab90
Timestamp: 1756005026 Timestamp [UCT]: 2025-08-24 03:10:26 Age [y:d:h:m:s]: 00:121:19:11:45
Block: 1353131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87024 RingCT/type: yes/0
Extra: 012be97e94fa1f9b710d74f3266262dd545f472d76ccfc2e89e55035f143dcab900211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84568a15ef7d8424b2a4801582ef8c78500b2bdf7fc834775f75df2ffac2289a 0.600000000000 1841104 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": 1353141, "vin": [ { "gen": { "height": 1353131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84568a15ef7d8424b2a4801582ef8c78500b2bdf7fc834775f75df2ffac2289a" } } ], "extra": [ 1, 43, 233, 126, 148, 250, 31, 155, 113, 13, 116, 243, 38, 98, 98, 221, 84, 95, 71, 45, 118, 204, 252, 46, 137, 229, 80, 53, 241, 67, 220, 171, 144, 2, 17, 0, 0, 0, 2, 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