Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64d1879cbe090bf8beac84c0fa76f74379b96e46495ba14b5c7cce8da6dcbcd

Tx prefix hash: b6fbc89df488d773e4f7b4c01d18e3e9b4c83163f78044c3aebacc134b56d366
Tx public key: a9431a8a5509b1b0b62fa7e52787cb258d16b4dba9a54a2567d8f53b44b320a4
Timestamp: 1699505481 Timestamp [UCT]: 2023-11-09 04:51:21 Age [y:d:h:m:s]: 01:334:07:08:21
Block: 887645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497780 RingCT/type: yes/0
Extra: 01a9431a8a5509b1b0b62fa7e52787cb258d16b4dba9a54a2567d8f53b44b320a4021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.702851599000 dcy

stealth address amount amount idx
00: 21bcc1fc51899a9d8cf68290ea93711b5ddae7fce1a0783b14cc28b11226b327 0.702851599000 1343538 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": 887655, "vin": [ { "gen": { "height": 887645 } } ], "vout": [ { "amount": 702851599, "target": { "key": "21bcc1fc51899a9d8cf68290ea93711b5ddae7fce1a0783b14cc28b11226b327" } } ], "extra": [ 1, 169, 67, 26, 138, 85, 9, 177, 176, 182, 47, 167, 229, 39, 135, 203, 37, 141, 22, 180, 219, 169, 165, 74, 37, 103, 216, 245, 59, 68, 179, 32, 164, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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