Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14a24086e681a076ef31782e3bf818ceb141b31c4216053e65a36770d4ad88be

Tx prefix hash: 036d991fa214f1dfb2a1cf737c33ab29ec1a76ade8757b9d910e4e9289590383
Tx public key: 36e8bba87caa8280bcd296b94cd2a03f25a959d747f6141c2243cafb021aa2e2
Timestamp: 1750486704 Timestamp [UCT]: 2025-06-21 06:18:24 Age [y:d:h:m:s]: 00:153:07:50:46
Block: 1309565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107430 RingCT/type: yes/0
Extra: 0136e8bba87caa8280bcd296b94cd2a03f25a959d747f6141c2243cafb021aa2e2021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc925bb555e5062eee3e5aeca6a929979a5e083926f0e95c8a013642d35789c1 0.600000000000 1797182 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": 1309575, "vin": [ { "gen": { "height": 1309565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc925bb555e5062eee3e5aeca6a929979a5e083926f0e95c8a013642d35789c1" } } ], "extra": [ 1, 54, 232, 187, 168, 124, 170, 130, 128, 188, 210, 150, 185, 76, 210, 160, 63, 37, 169, 89, 215, 71, 246, 20, 28, 34, 67, 202, 251, 2, 26, 162, 226, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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