Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84d6dc303f7f4100f94445669346c5f1ad2271c58427e629b43a475b733123de

Tx prefix hash: f441b91dd7fbee8b7e5974f127e65fed001ec281fbd621b1e99a0b3bce6d927a
Tx public key: 15caeb486d7a80a706c3859551969c5ba5ae30aa92d75c7f0ff1c1698f4a3d84
Timestamp: 1764062382 Timestamp [UCT]: 2025-11-25 09:19:42 Age [y:d:h:m:s]: 00:002:19:35:27
Block: 1419730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2014 RingCT/type: yes/0
Extra: 0115caeb486d7a80a706c3859551969c5ba5ae30aa92d75c7f0ff1c1698f4a3d84021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e4bb29ae355a4dd0372356317a3da867e2eed33670e58cedef5721b25e11616 0.600000000000 1908271 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": 1419740, "vin": [ { "gen": { "height": 1419730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e4bb29ae355a4dd0372356317a3da867e2eed33670e58cedef5721b25e11616" } } ], "extra": [ 1, 21, 202, 235, 72, 109, 122, 128, 167, 6, 195, 133, 149, 81, 150, 156, 91, 165, 174, 48, 170, 146, 215, 92, 127, 15, 241, 193, 105, 143, 74, 61, 132, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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