Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5d8c01f076993f56e9edcbd30d4abe6bb6aa97da91a88c288c015ad6ed93b0

Tx prefix hash: 87db54c3b6f562b1aaa53d1678716514f8f8342ed4e7d1cdbda32480ae46e8a6
Tx public key: ecc3a3e0712a8d20a4f12e8cc501fc7b94a36e67c5b8a593a73b44d7cff21fb4
Timestamp: 1792285720 Timestamp [UTC]: 2026-10-18 01:08:40 Age [y:d:h:m:s]: 00:035:04:40:37
Block: 1656793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 26701 RingCT/type: yes/0
Extra: 01ecc3a3e0712a8d20a4f12e8cc501fc7b94a36e67c5b8a593a73b44d7cff21fb4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 513a386d0042fdc3bab2db817239c348fc94e1c7b2d6f29532b02e3a144d3e55 0.000600000000 2147551 of 15 <63>

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": 1656803, "vin": [ { "gen": { "height": 1656793 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "513a386d0042fdc3bab2db817239c348fc94e1c7b2d6f29532b02e3a144d3e55", "view_tag": "63" } } } ], "extra": [ 1, 236, 195, 163, 224, 113, 42, 141, 32, 164, 241, 46, 140, 197, 1, 252, 123, 148, 163, 110, 103, 197, 184, 165, 147, 167, 59, 68, 215, 207, 242, 31, 180 ], "rct_signatures": { "type": 0 } }


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