Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ef060ad4fb2bb8f6ef2ad29d7f7ad7f1ecf17db0a9b0b320a829da3d438a34

Tx prefix hash: 95911e25cb79e634e0f0c975e556a64c9d376362c76187778feda4d8c35397a5
Tx public key: 78f2e0d45ad429185583953e6d26ddc732a8e0eaae32bb3ca31d8d81df93ae0a
Timestamp: 1785940016 Timestamp [UTC]: 2026-08-05 14:26:56 Age [y:d:h:m:s]: 00:109:03:26:26
Block: 1606536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 76958 RingCT/type: yes/0
Extra: 0178f2e0d45ad429185583953e6d26ddc732a8e0eaae32bb3ca31d8d81df93ae0a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a87775250e025a05f3d71d3e2d391ed605c6c8f762875c52c45f9d9d20c9d778 0.000600000000 2096556 of 15 <5f>

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": 1606546, "vin": [ { "gen": { "height": 1606536 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a87775250e025a05f3d71d3e2d391ed605c6c8f762875c52c45f9d9d20c9d778", "view_tag": "5f" } } } ], "extra": [ 1, 120, 242, 224, 212, 90, 212, 41, 24, 85, 131, 149, 62, 109, 38, 221, 199, 50, 168, 224, 234, 174, 50, 187, 60, 163, 29, 141, 129, 223, 147, 174, 10 ], "rct_signatures": { "type": 0 } }


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