Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8d66f3f8d7ad5511a5ec03e5ea67292b61e7f87e252c7423ed3350c45a3f8d0

Tx prefix hash: fcdc54c6e0788a50c46f467b8c19b91ff8cfe7eb4087ddb51d0d3bd331b6b8d5
Tx public key: b09f3be20b0e9517f3a2e2e0052770785d29af9e96e8eab0d99364543501889f
Timestamp: 1781677789 Timestamp [UTC]: 2026-06-17 06:29:49 Age [y:d:h:m:s]: 00:158:16:07:48
Block: 1561306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 122844 RingCT/type: yes/0
Extra: 01b09f3be20b0e9517f3a2e2e0052770785d29af9e96e8eab0d99364543501889f02089b90f587a49b5364

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ef82b8156127207be494406f26aa773d52545dc2f561423acaa47234e37e927 0.000600000000 2051284 of 15 <47>

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": 1561316, "vin": [ { "gen": { "height": 1561306 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6ef82b8156127207be494406f26aa773d52545dc2f561423acaa47234e37e927", "view_tag": "47" } } } ], "extra": [ 1, 176, 159, 59, 226, 11, 14, 149, 23, 243, 162, 226, 224, 5, 39, 112, 120, 93, 41, 175, 158, 150, 232, 234, 176, 217, 147, 100, 84, 53, 1, 136, 159, 2, 8, 155, 144, 245, 135, 164, 155, 83, 100 ], "rct_signatures": { "type": 0 } }


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