Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26566f0b0b0dccbd5f371ec1c19dea761303bf2f2d179789d8349508775eead5

Tx prefix hash: b6164133347ad0c982498d43f3bd5d06e1ca8bf2718951f193a7537a0ffa0fc2
Tx public key: c341139c8b2c58bd6f58a837f7002b839b00584c3905ab95767f1103a8bb8890
Timestamp: 1758429452 Timestamp [UTC]: 2025-09-21 04:37:32 Age [y:d:h:m:s]: 01:056:18:33:50
Block: 1373043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306944 RingCT/type: yes/0
Extra: 01c341139c8b2c58bd6f58a837f7002b839b00584c3905ab95767f1103a8bb8890021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 626398eafa93da2dbd2a5e438e45717a249e8d07d0fbc5bab09b2d7770e975cb 0.000600000000 1861128 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": 1373053, "vin": [ { "gen": { "height": 1373043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "626398eafa93da2dbd2a5e438e45717a249e8d07d0fbc5bab09b2d7770e975cb" } } ], "extra": [ 1, 195, 65, 19, 156, 139, 44, 88, 189, 111, 88, 168, 55, 247, 0, 43, 131, 155, 0, 88, 76, 57, 5, 171, 149, 118, 127, 17, 3, 168, 187, 136, 144, 2, 17, 0, 0, 0, 1, 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: