Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db18e710ede738754adc1e3a4a8064f80c6187f8011d56d4e2c8c859e8207e60

Tx prefix hash: 3b9dc4ace724e01eb2f5175edd4e571cb859128d6b855e663b53d9864c893d54
Tx public key: 8bffe96670c66b94e7c5c2ac5ac480b4950dc305a0353014469978c1b15834df
Timestamp: 1577712093 Timestamp [UTC]: 2019-12-30 13:21:33 Age [y:d:h:m:s]: 06:135:22:15:33
Block: 35049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1497770 RingCT/type: yes/0
Extra: 018bffe96670c66b94e7c5c2ac5ac480b4950dc305a0353014469978c1b15834df0211000000018a2ee0d9000000000000000000

1 output(s) for total of 0.469752357528 xmr

stealth address amount amount idx tag
00: f7b28c8c83d3ed18840c7f25b24175a8db111bd7264851449b7b1a54e14b54b3 0.469752357528 59042 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 dinastycoin-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": 35059, "vin": [ { "gen": { "height": 35049 } } ], "vout": [ { "amount": 469752357528, "target": { "key": "f7b28c8c83d3ed18840c7f25b24175a8db111bd7264851449b7b1a54e14b54b3" } } ], "extra": [ 1, 139, 255, 233, 102, 112, 198, 107, 148, 231, 197, 194, 172, 90, 196, 128, 180, 149, 13, 195, 5, 160, 53, 48, 20, 70, 153, 120, 193, 177, 88, 52, 223, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: