Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e1335b9ef4738d8d53542c6772966db9a229daf072fd989f00a8bf069cd939c

Tx prefix hash: d42b5f667ead5663573f4b459ee4609b51f8070d7e1ed0587606ff64d56eeae3
Tx public key: 3ac18fdb95ba1fdeafb682d7af4de4bdd78fd81b7d970f1e9ebc495e4f89de70
Timestamp: 1744576352 Timestamp [UCT]: 2025-04-13 20:32:32 Age [y:d:h:m:s]: 00:221:05:07:05
Block: 1260805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155813 RingCT/type: yes/0
Extra: 013ac18fdb95ba1fdeafb682d7af4de4bdd78fd81b7d970f1e9ebc495e4f89de70021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38f39a3ca449535b221dd562cf5e43f9c954c36e14ede786ce89a723a8eebde3 0.600000000000 1747968 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": 1260815, "vin": [ { "gen": { "height": 1260805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38f39a3ca449535b221dd562cf5e43f9c954c36e14ede786ce89a723a8eebde3" } } ], "extra": [ 1, 58, 193, 143, 219, 149, 186, 31, 222, 175, 182, 130, 215, 175, 77, 228, 189, 215, 143, 216, 27, 125, 151, 15, 30, 158, 188, 73, 94, 79, 137, 222, 112, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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