Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a5a39dc7cf3151c484476cb85b0dffd9dbac22851545594015951ba7540d60

Tx prefix hash: 13094a7ec7a94e6c773ac408f6c7a2410dda0070acfe16dba524d9599e302fb6
Tx public key: afe2d7f4a693bf9dd518f0d3fcab3eb98ca55ecbfb71a3e18bd9651e8ad56c9e
Timestamp: 1745971626 Timestamp [UCT]: 2025-04-30 00:07:06 Age [y:d:h:m:s]: 00:022:14:39:08
Block: 1272359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16180 RingCT/type: yes/0
Extra: 01afe2d7f4a693bf9dd518f0d3fcab3eb98ca55ecbfb71a3e18bd9651e8ad56c9e0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ec2ce6afcaf07a1984b5cdab21a3ece043b817ba9aa945021a8950b3430fe6 0.600000000000 1759634 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": 1272369, "vin": [ { "gen": { "height": 1272359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ec2ce6afcaf07a1984b5cdab21a3ece043b817ba9aa945021a8950b3430fe6" } } ], "extra": [ 1, 175, 226, 215, 244, 166, 147, 191, 157, 213, 24, 240, 211, 252, 171, 62, 185, 140, 165, 94, 203, 251, 113, 163, 225, 139, 217, 101, 30, 138, 213, 108, 158, 2, 17, 0, 0, 0, 1, 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