Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af7d9808e6024b0be1ab967982cf2b4af0d2c29f96b96edca4796857a9eb6357

Tx prefix hash: 1aba8f7d989e83957b0819830b2c6adab547c435ecadbda6f9faa605cb7cad65
Tx public key: 240ecb9e8ac8abc2077f72b969c3692e0e30971c1e1d83b86029a7cbcc7e25ce
Timestamp: 1762060147 Timestamp [UCT]: 2025-11-02 05:09:07 Age [y:d:h:m:s]: 00:004:17:07:32
Block: 1403140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3365 RingCT/type: yes/0
Extra: 01240ecb9e8ac8abc2077f72b969c3692e0e30971c1e1d83b86029a7cbcc7e25ce021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9887695caca3f19ae4aa6fa6408325ce74de49727076aa5f6d59d98d40c30e4c 0.600000000000 1891467 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": 1403150, "vin": [ { "gen": { "height": 1403140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9887695caca3f19ae4aa6fa6408325ce74de49727076aa5f6d59d98d40c30e4c" } } ], "extra": [ 1, 36, 14, 203, 158, 138, 200, 171, 194, 7, 127, 114, 185, 105, 195, 105, 46, 14, 48, 151, 28, 30, 29, 131, 184, 96, 41, 167, 203, 204, 126, 37, 206, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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