Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e26568f7cbd9d04f7c0272482225d1e4187f2ceb6b9401984ee2aeb24fd89d2

Tx prefix hash: 522ff066f979eccccf46d6384a49f2b3f377fc18dbb6b004fdcf8f341975f4e3
Tx public key: df49a0c367be1e93e64a4cdc8812117aa875bad7fe33b9412150ef26b6996c6e
Timestamp: 1789513032 Timestamp [UTC]: 2026-09-15 22:57:12 Age [y:d:h:m:s]: 00:062:19:27:23
Block: 1636313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 44244 RingCT/type: yes/0
Extra: 01df49a0c367be1e93e64a4cdc8812117aa875bad7fe33b9412150ef26b6996c6e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6270fdc2c3fe2f6982475625b0a3b4a032b0e609d7b79edadcde6d7758faddf5 0.000600000000 2126343 of 15 <83>

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": 1636323, "vin": [ { "gen": { "height": 1636313 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6270fdc2c3fe2f6982475625b0a3b4a032b0e609d7b79edadcde6d7758faddf5", "view_tag": "83" } } } ], "extra": [ 1, 223, 73, 160, 195, 103, 190, 30, 147, 230, 74, 76, 220, 136, 18, 17, 122, 168, 117, 186, 215, 254, 51, 185, 65, 33, 80, 239, 38, 182, 153, 108, 110 ], "rct_signatures": { "type": 0 } }


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