Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0dfde73a4018aaab648db0ecd22cfe954c1a575268eeb5a63231f426b2bfbb2

Tx prefix hash: 4c164d1e51407403ff68ddd736dc79bf7e6b99639c14d267cf722fa43e8c92fb
Tx public key: 4ac7c6e9c9b03c027c380b3c8524c9b316f99f5717e4a2bf584d1057c92b59a8
Timestamp: 1774820662 Timestamp [UTC]: 2026-03-29 21:44:22 Age [y:d:h:m:s]: 00:233:23:21:01
Block: 1508635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172749 RingCT/type: yes/0
Extra: 014ac7c6e9c9b03c027c380b3c8524c9b316f99f5717e4a2bf584d1057c92b59a8021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 11fe54bda01d280e93dac1d315c43b8783d120e21afd308f99514f8b56ed83e3 0.000600000000 1998389 of 15 -

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": 1508645, "vin": [ { "gen": { "height": 1508635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11fe54bda01d280e93dac1d315c43b8783d120e21afd308f99514f8b56ed83e3" } } ], "extra": [ 1, 74, 199, 198, 233, 201, 176, 60, 2, 124, 56, 11, 60, 133, 36, 201, 179, 22, 249, 159, 87, 23, 228, 162, 191, 88, 77, 16, 87, 201, 43, 89, 168, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: