Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51be4d6a6b34c3186ec409ea68ce85dc2c89900b6ae21e5e323d98bee566ad91

Tx prefix hash: 4288ee0576c307e6aaa96748f2ee83825e8fa8130b7b12120e5176bcdd744b86
Tx public key: 43549bcf235377a3ad6e6b4ca7829b5e7ef288f1d60b3b4c605ae2bb580f33e2
Timestamp: 1707274825 Timestamp [UCT]: 2024-02-07 03:00:25 Age [y:d:h:m:s]: 01:070:01:05:56
Block: 952051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311117 RingCT/type: yes/0
Extra: 0143549bcf235377a3ad6e6b4ca7829b5e7ef288f1d60b3b4c605ae2bb580f33e202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfff6835a3af0c550382ce169a5124c550354dee5e553dcffe8c035b1bf55bc9 0.600000000000 1410923 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": 952061, "vin": [ { "gen": { "height": 952051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfff6835a3af0c550382ce169a5124c550354dee5e553dcffe8c035b1bf55bc9" } } ], "extra": [ 1, 67, 84, 155, 207, 35, 83, 119, 163, 173, 110, 107, 76, 167, 130, 155, 94, 126, 242, 136, 241, 214, 11, 59, 76, 96, 90, 226, 187, 88, 15, 51, 226, 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