Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 382aaefc151af2a4958b7a53c4ed7ab9fb32b8764678a55a15fe725ed0cd04a2

Tx prefix hash: 7f68a9db55933f1dd86ccf767f4929256264d1c442d26e19197624e759933493
Tx public key: 396a27f0a293b4acf63c5f7613de87f37685a5462f2f8ad116e831ddfb543ea1
Timestamp: 1760475444 Timestamp [UTC]: 2025-10-14 20:57:24 Age [y:d:h:m:s]: 01:035:18:23:34
Block: 1389997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291977 RingCT/type: yes/0
Extra: 01396a27f0a293b4acf63c5f7613de87f37685a5462f2f8ad116e831ddfb543ea102110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88e7eb06721be90f1e3e06d6342e0d7731f0e0329d2c4aa37982ca7d532fac13 0.000600000000 1878228 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": 1390007, "vin": [ { "gen": { "height": 1389997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88e7eb06721be90f1e3e06d6342e0d7731f0e0329d2c4aa37982ca7d532fac13" } } ], "extra": [ 1, 57, 106, 39, 240, 162, 147, 180, 172, 246, 60, 95, 118, 19, 222, 135, 243, 118, 133, 165, 70, 47, 47, 138, 209, 22, 232, 49, 221, 251, 84, 62, 161, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: