Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b7b0fe5dff3b41d37cd2c9c7301b3e88443260b78122b4bb196f1eabfe2069

Tx prefix hash: 8702933f616ffd525170313d4687f52b92b240e8800e0f105b4961b25fbc2e6b
Tx public key: f42df81c1b51166b613692c7d21828b71181385219f6746f063e1dbb94ca78e9
Timestamp: 1790096757 Timestamp [UTC]: 2026-09-22 17:05:57 Age [y:d:h:m:s]: 00:056:20:35:40
Block: 1641213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 39955 RingCT/type: yes/0
Extra: 01f42df81c1b51166b613692c7d21828b71181385219f6746f063e1dbb94ca78e9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7dc0175249033d464f2d1f7652bf96007e49d58feb1cb83d4c4e850e637277f7 0.000600000000 2131255 of 15 <11>

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": 1641223, "vin": [ { "gen": { "height": 1641213 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "7dc0175249033d464f2d1f7652bf96007e49d58feb1cb83d4c4e850e637277f7", "view_tag": "11" } } } ], "extra": [ 1, 244, 45, 248, 28, 27, 81, 22, 107, 97, 54, 146, 199, 210, 24, 40, 183, 17, 129, 56, 82, 25, 246, 116, 111, 6, 62, 29, 187, 148, 202, 120, 233 ], "rct_signatures": { "type": 0 } }


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