Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e9226fff3e8369181353d1e0de03ee1fc794f9b1d6adc214624703130f48e0c

Tx prefix hash: ca4d666cd55eb6b84f54abdf8eda231bbea5b5280c83826373db6f370670ae0c
Tx public key: bc61a873ca3e297169b529d38c491e9e5a8aeb6f8d2aedff967ec1c59e907e73
Timestamp: 1708579413 Timestamp [UCT]: 2024-02-22 05:23:33 Age [y:d:h:m:s]: 01:047:11:22:35
Block: 962870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294955 RingCT/type: yes/0
Extra: 01bc61a873ca3e297169b529d38c491e9e5a8aeb6f8d2aedff967ec1c59e907e7302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a8b39f324615c9c7838f4779e53f96b1213f64a31a22fa88fc91492a63cc979 0.600000000000 1422557 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": 962880, "vin": [ { "gen": { "height": 962870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a8b39f324615c9c7838f4779e53f96b1213f64a31a22fa88fc91492a63cc979" } } ], "extra": [ 1, 188, 97, 168, 115, 202, 62, 41, 113, 105, 181, 41, 211, 140, 73, 30, 158, 90, 138, 235, 111, 141, 42, 237, 255, 150, 126, 193, 197, 158, 144, 126, 115, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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