Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeb57f0ad3fd811e706095704fc8957ce502380a56129098b1128613f00db9e8

Tx prefix hash: 808eae7908cfa9a7ce28964fe935e1b2681506c7337b4c0b13643eee8cc78e69
Tx public key: 6e2f6db8b1f9b4dbbaf3afa26d5cd5c3c573c4e9f40b1282da04383ea169558e
Timestamp: 1748009065 Timestamp [UCT]: 2025-05-23 14:04:25 Age [y:d:h:m:s]: 00:174:18:46:05
Block: 1289227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122613 RingCT/type: yes/0
Extra: 016e2f6db8b1f9b4dbbaf3afa26d5cd5c3c573c4e9f40b1282da04383ea169558e0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94317c37cc99417ba759d25659efced62140c9ae365e15076aa47c37483bc5bc 0.600000000000 1776694 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": 1289237, "vin": [ { "gen": { "height": 1289227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94317c37cc99417ba759d25659efced62140c9ae365e15076aa47c37483bc5bc" } } ], "extra": [ 1, 110, 47, 109, 184, 177, 249, 180, 219, 186, 243, 175, 162, 109, 92, 213, 195, 197, 115, 196, 233, 244, 11, 18, 130, 218, 4, 56, 62, 161, 105, 85, 142, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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