Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6171603e43954649c9855d96470b2f16e93cc7d6cb4d37ee00bbafb1a6f3438

Tx prefix hash: 698473057ebdcf4eb28694d0d8a2cc9ea91439bbbd061eeae572d61d1b79def3
Tx public key: ed70ebfacc30ef806121d2f693663c40b923dd0b3edd9dcb98d7cca1c0f5bd12
Timestamp: 1706625712 Timestamp [UCT]: 2024-01-30 14:41:52 Age [y:d:h:m:s]: 01:001:07:20:38
Block: 946653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261990 RingCT/type: yes/0
Extra: 01ed70ebfacc30ef806121d2f693663c40b923dd0b3edd9dcb98d7cca1c0f5bd120211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e663bddb7d0d087c180816ac6a626ff6385b593651946423b761ca5c3b5681c9 0.600000000000 1404987 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": 946663, "vin": [ { "gen": { "height": 946653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e663bddb7d0d087c180816ac6a626ff6385b593651946423b761ca5c3b5681c9" } } ], "extra": [ 1, 237, 112, 235, 250, 204, 48, 239, 128, 97, 33, 210, 246, 147, 102, 60, 64, 185, 35, 221, 11, 62, 221, 157, 203, 152, 215, 204, 161, 192, 245, 189, 18, 2, 17, 0, 0, 0, 5, 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