Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a68738d2d31c02b24f2e8eee885be366f34d61a89bf578335ccdb397037e3dc1

Tx prefix hash: f1a2f101fa3426b33cfe313de0bc950a15e0ab4af2aa26e67307e64eba4b06ae
Tx public key: 3a738c458ecd7ff817e752d3998c6a0eff8a5560f06355b2164b8b200f7c56b6
Timestamp: 1741927140 Timestamp [UTC]: 2025-03-14 04:39:00 Age [y:d:h:m:s]: 01:056:14:14:15
Block: 1238888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291662 RingCT/type: yes/0
Extra: 013a738c458ecd7ff817e752d3998c6a0eff8a5560f06355b2164b8b200f7c56b60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba84e9fff558fcd226ea5ed3c5cc98efe7f10f1f4c73011f5f8dbe3bec1d9f21 0.000600000000 1725851 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": 1238898, "vin": [ { "gen": { "height": 1238888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba84e9fff558fcd226ea5ed3c5cc98efe7f10f1f4c73011f5f8dbe3bec1d9f21" } } ], "extra": [ 1, 58, 115, 140, 69, 142, 205, 127, 248, 23, 231, 82, 211, 153, 140, 106, 14, 255, 138, 85, 96, 240, 99, 85, 178, 22, 75, 139, 32, 15, 124, 86, 182, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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: