Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df9d1f6724f53fdf996a7f3d7b50d71084c07b549dd32c46e7d5b92fbc7034b3

Tx prefix hash: cf7b61defac8c12ccdf53157c3c8808a5284aac5a3c265d75bbee349d43c6068
Tx public key: 0bf541b063d3a02d2c1c3848059f632fdccb92bc2e2399b3d36f91b992062450
Timestamp: 1634935704 Timestamp [UTC]: 2021-10-22 20:48:24 Age [y:d:h:m:s]: 04:206:13:14:35
Block: 358350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176670 RingCT/type: yes/0
Extra: 010bf541b063d3a02d2c1c3848059f632fdccb92bc2e2399b3d36f91b99206245002110000000bf60c5d7e000000000000000000

1 output(s) for total of 0.039869253414 xmr

stealth address amount amount idx tag
00: 2b119df835f1fb69da82506e468552a5d41398c16384f8ae2690a4d9cf21f66f 0.039869253414 730223 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": 358360, "vin": [ { "gen": { "height": 358350 } } ], "vout": [ { "amount": 39869253414, "target": { "key": "2b119df835f1fb69da82506e468552a5d41398c16384f8ae2690a4d9cf21f66f" } } ], "extra": [ 1, 11, 245, 65, 176, 99, 211, 160, 45, 44, 28, 56, 72, 5, 159, 99, 47, 220, 203, 146, 188, 46, 35, 153, 179, 211, 111, 145, 185, 146, 6, 36, 80, 2, 17, 0, 0, 0, 11, 246, 12, 93, 126, 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: