Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fff4a582460bc64d0bfbeeb0406197fb64590b0a2fe38136a8c9f570909d08a4

Tx prefix hash: 3ce2df44bf1ff3fff1921d3bfe24aa68e1a58821948b60369f43c59add11c85d
Tx public key: 69491896f189bfa8e2779811450904ac41ab3aaf1f8f7d26467369c766191b2c
Timestamp: 1743887974 Timestamp [UTC]: 2025-04-05 21:19:34 Age [y:d:h:m:s]: 01:224:10:51:17
Block: 1255098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424416 RingCT/type: yes/0
Extra: 0169491896f189bfa8e2779811450904ac41ab3aaf1f8f7d26467369c766191b2c0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0c1d8785c69b3944611b956a41fd409abd0aba3fc41593a332b40f6cdf9a86f3 0.000600000000 1742201 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": 1255108, "vin": [ { "gen": { "height": 1255098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c1d8785c69b3944611b956a41fd409abd0aba3fc41593a332b40f6cdf9a86f3" } } ], "extra": [ 1, 105, 73, 24, 150, 241, 137, 191, 168, 226, 119, 152, 17, 69, 9, 4, 172, 65, 171, 58, 175, 31, 143, 125, 38, 70, 115, 105, 199, 102, 25, 27, 44, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: