Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785e89b0d23bcd1ff544590430858eeebfde0b7f30e5933b4abc767ac15988b1

Tx prefix hash: 5602de8ccb783bb415fcefd970ff27db8f64e79675cdc7c1f796aa52b848f528
Tx public key: 673d9764215c29c6c50320af36399e41f30fd0099e9e3458572b0bb6dbada2f3
Timestamp: 1696463599 Timestamp [UCT]: 2023-10-04 23:53:19 Age [y:d:h:m:s]: 02:038:12:39:05
Block: 862623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547176 RingCT/type: yes/0
Extra: 01673d9764215c29c6c50320af36399e41f30fd0099e9e3458572b0bb6dbada2f3021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.850691214000 dcy

stealth address amount amount idx
00: 9f6d2a9447d784283b00e66f346854c706e3e34ed0361cb719cac934be0ec5b4 0.850691214000 1317051 of 0

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": 862633, "vin": [ { "gen": { "height": 862623 } } ], "vout": [ { "amount": 850691214, "target": { "key": "9f6d2a9447d784283b00e66f346854c706e3e34ed0361cb719cac934be0ec5b4" } } ], "extra": [ 1, 103, 61, 151, 100, 33, 92, 41, 198, 197, 3, 32, 175, 54, 57, 158, 65, 243, 15, 208, 9, 158, 158, 52, 88, 87, 43, 11, 182, 219, 173, 162, 243, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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