Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96bd68b8d5efa6579a964ba41142e6332da2933748fa20e897bf8e39351a3f4b

Tx prefix hash: 2bef96aa43e18b8bcb0aa2dca7f93191e90f793796ebaa3a8265e7ac7eef9e07
Tx public key: 1f06af01f2718de5bc2892002c5ec0954d50035bf27ac6e50817ef55271ca42a
Timestamp: 1758579424 Timestamp [UTC]: 2025-09-22 22:17:04 Age [y:d:h:m:s]: 00:299:08:21:07
Block: 1374294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208820 RingCT/type: yes/0
Extra: 011f06af01f2718de5bc2892002c5ec0954d50035bf27ac6e50817ef55271ca42a021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f85af2e07fee7c9cdcc4e511011eeb229e16b8004eb2bac3c5a90485c0f1efa 0.000600000000 1862379 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": 1374304, "vin": [ { "gen": { "height": 1374294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f85af2e07fee7c9cdcc4e511011eeb229e16b8004eb2bac3c5a90485c0f1efa" } } ], "extra": [ 1, 31, 6, 175, 1, 242, 113, 141, 229, 188, 40, 146, 0, 44, 94, 192, 149, 77, 80, 3, 91, 242, 122, 198, 229, 8, 23, 239, 85, 39, 28, 164, 42, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: