Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea2d037d6120348d2016feb54a88ac4e421a431ddfc9aafa83b73241cb6cc30

Tx prefix hash: 5848b093445f944feb59918b4d7b62af394f70b1e8c679a3dfd66709bae4ffb1
Tx public key: 93a4331c425ea9b927117032bb091fd3a5109f1c05fa5ef49ce32d5eb8d98321
Timestamp: 1759576004 Timestamp [UCT]: 2025-10-04 11:06:44 Age [y:d:h:m:s]: 00:087:07:39:03
Block: 1382546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62520 RingCT/type: yes/0
Extra: 0193a4331c425ea9b927117032bb091fd3a5109f1c05fa5ef49ce32d5eb8d98321021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41afefc094d162aa1151d8104d6153a7aa5d13aceaf3d44680edc2ab304913ab 0.600000000000 1870681 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": 1382556, "vin": [ { "gen": { "height": 1382546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41afefc094d162aa1151d8104d6153a7aa5d13aceaf3d44680edc2ab304913ab" } } ], "extra": [ 1, 147, 164, 51, 28, 66, 94, 169, 185, 39, 17, 112, 50, 187, 9, 31, 211, 165, 16, 159, 28, 5, 250, 94, 244, 156, 227, 45, 94, 184, 217, 131, 33, 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