Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cf334f35717363c14cf9034155582baf32acd452d661240f24677fdf1a0b553

Tx prefix hash: 6e56bfd7e489bcbebb59c0aa35426988062a29a34b1763c13e9ae9b866024f3b
Tx public key: 9a3b0a65a5eff9dc1ddc2d7f96779731f9fd53117b656999891cace10e797e31
Timestamp: 1708318162 Timestamp [UCT]: 2024-02-19 04:49:22 Age [y:d:h:m:s]: 01:274:23:58:08
Block: 960709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455301 RingCT/type: yes/0
Extra: 019a3b0a65a5eff9dc1ddc2d7f96779731f9fd53117b656999891cace10e797e310211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3937fb3cb2c746363982fe25ab3dc99bcd3b7643ce790d652330ee4e85c506f0 0.600000000000 1420296 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": 960719, "vin": [ { "gen": { "height": 960709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3937fb3cb2c746363982fe25ab3dc99bcd3b7643ce790d652330ee4e85c506f0" } } ], "extra": [ 1, 154, 59, 10, 101, 165, 239, 249, 220, 29, 220, 45, 127, 150, 119, 151, 49, 249, 253, 83, 17, 123, 101, 105, 153, 137, 28, 172, 225, 14, 121, 126, 49, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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