Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ec197e4a8aaf1ee50ceb7b46455cd1fca3e537e062bd494be25c985f4c12739

Tx prefix hash: bece6fe65f2a1929515c392e655176f87dc3a9eae44b10f7472eb36d2496d3ce
Tx public key: 5cf673271f3c7ac4971038e593a541d9bf69ff0025c787dbe3389f3c81c9cf8d
Timestamp: 1697268899 Timestamp [UCT]: 2023-10-14 07:34:59 Age [y:d:h:m:s]: 01:101:08:26:40
Block: 869305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333646 RingCT/type: yes/0
Extra: 015cf673271f3c7ac4971038e593a541d9bf69ff0025c787dbe3389f3c81c9cf8d021100000001faf35c9c000000000000000000

1 output(s) for total of 0.808410038000 dcy

stealth address amount amount idx
00: 7bf9a24c47bb25462cbbdd3535b307682acf248a5c6f5ab26087372bac618ba6 0.808410038000 1324146 of 0

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": 869315, "vin": [ { "gen": { "height": 869305 } } ], "vout": [ { "amount": 808410038, "target": { "key": "7bf9a24c47bb25462cbbdd3535b307682acf248a5c6f5ab26087372bac618ba6" } } ], "extra": [ 1, 92, 246, 115, 39, 31, 60, 122, 196, 151, 16, 56, 229, 147, 165, 65, 217, 191, 105, 255, 0, 37, 199, 135, 219, 227, 56, 159, 60, 129, 201, 207, 141, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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