Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1696b871518cb64e872cf4cc36731460a917e75a412e91e5b91cdbaff53e5d20

Tx prefix hash: ce3d5846dadd1b95faf4950089211dfd9b7c6dc3631204c633b18a8781a59b99
Tx public key: 97f86544d6fd5ab236ff3a59f7ac884f504d7a103c61c7ce779d11205e82ec91
Timestamp: 1744322621 Timestamp [UCT]: 2025-04-10 22:03:41 Age [y:d:h:m:s]: 00:032:01:12:24
Block: 1258700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22922 RingCT/type: yes/0
Extra: 0197f86544d6fd5ab236ff3a59f7ac884f504d7a103c61c7ce779d11205e82ec91021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d002ed9ad6239e0cb4cfc4c76916d4875482e61394b1a70d94cd9f5c7e44fab2 0.600000000000 1745837 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": 1258710, "vin": [ { "gen": { "height": 1258700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d002ed9ad6239e0cb4cfc4c76916d4875482e61394b1a70d94cd9f5c7e44fab2" } } ], "extra": [ 1, 151, 248, 101, 68, 214, 253, 90, 178, 54, 255, 58, 89, 247, 172, 136, 79, 80, 77, 122, 16, 60, 97, 199, 206, 119, 157, 17, 32, 94, 130, 236, 145, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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