Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 076cbbd71fac56f19397fd844eba93da795b35a37b6c1a7b4be238e22c3032f6

Tx prefix hash: 9c62f3760fc97d06792443c3cf2d6e4564ae6628ad419ffb0b24564bd04e0d86
Tx public key: a800257e5e6717a57eebe015e288a8b633d63827c45fe52ca4d0198f6b97a0bf
Timestamp: 1710865388 Timestamp [UCT]: 2024-03-19 16:23:08 Age [y:d:h:m:s]: 01:044:07:27:11
Block: 981850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292643 RingCT/type: yes/0
Extra: 01a800257e5e6717a57eebe015e288a8b633d63827c45fe52ca4d0198f6b97a0bf02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a25968a388476f79fb3cd8d22d0806219f7a05df41e7254d5b672e7762d2c975 0.600000000000 1441949 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": 981860, "vin": [ { "gen": { "height": 981850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a25968a388476f79fb3cd8d22d0806219f7a05df41e7254d5b672e7762d2c975" } } ], "extra": [ 1, 168, 0, 37, 126, 94, 103, 23, 165, 126, 235, 224, 21, 226, 136, 168, 182, 51, 214, 56, 39, 196, 95, 229, 44, 164, 208, 25, 143, 107, 151, 160, 191, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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