Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce94e488ae3d2bc217a1c03069c61bfd0160a889b7c84596bb50fd4f2ac4915c

Tx prefix hash: bccf7d43d85f93ee720a8ffec30656fa88a0980caef0bca6eca20d062965f9ed
Tx public key: a9206a14f95907c5e4f2276081f543a799da7e96fb69a4766cabb491477b0730
Timestamp: 1742065115 Timestamp [UTC]: 2025-03-15 18:58:35 Age [y:d:h:m:s]: 01:065:17:01:35
Block: 1240034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298938 RingCT/type: yes/0
Extra: 01a9206a14f95907c5e4f2276081f543a799da7e96fb69a4766cabb491477b07300211000000091f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f13a0ee3e20880306eff5ad5ce5140d59dc026baab5b569bd3c7e65f51c3d8b1 0.000600000000 1726999 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": 1240044, "vin": [ { "gen": { "height": 1240034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f13a0ee3e20880306eff5ad5ce5140d59dc026baab5b569bd3c7e65f51c3d8b1" } } ], "extra": [ 1, 169, 32, 106, 20, 249, 89, 7, 197, 228, 242, 39, 96, 129, 245, 67, 167, 153, 218, 126, 150, 251, 105, 164, 118, 108, 171, 180, 145, 71, 123, 7, 48, 2, 17, 0, 0, 0, 9, 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: