Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb77ed04bdc97e6ef77a6dff04496d90f18d2984b90301c344ccdb9d494949bb

Tx prefix hash: 79ba9ee1098e1a85ea663aebacbce0977a6ef52c06e51a3e03865764b4c03c3d
Tx public key: 82b1c46c6b7943a7597d26a22a901727f32f944fd4b5cce50d0cf08596d32536
Timestamp: 1707624953 Timestamp [UCT]: 2024-02-11 04:15:53 Age [y:d:h:m:s]: 01:055:06:43:49
Block: 954950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300559 RingCT/type: yes/0
Extra: 0182b1c46c6b7943a7597d26a22a901727f32f944fd4b5cce50d0cf08596d3253602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b0e9de0bd0635f6b04b14081b15b7d5ebc050cb817fa7f405d874d419d9832d 0.600000000000 1414232 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": 954960, "vin": [ { "gen": { "height": 954950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b0e9de0bd0635f6b04b14081b15b7d5ebc050cb817fa7f405d874d419d9832d" } } ], "extra": [ 1, 130, 177, 196, 108, 107, 121, 67, 167, 89, 125, 38, 162, 42, 144, 23, 39, 243, 47, 148, 79, 212, 181, 204, 229, 13, 12, 240, 133, 150, 211, 37, 54, 2, 17, 0, 0, 0, 4, 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