Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61df1faa8fa982d05df077496a44e074866b7a001d1f4100befaacf45656ae40

Tx prefix hash: 18a664919ba2ed11b92900b10e0f8c12a41bf7deff93623da44ed8e33b7a3c40
Tx public key: 93b53babe374bc7f8b0a0e42ea6544a68bd4920608261be5004c6db99437f05e
Timestamp: 1773270157 Timestamp [UTC]: 2026-03-11 23:02:37 Age [y:d:h:m:s]: 00:250:13:39:18
Block: 1495809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184571 RingCT/type: yes/0
Extra: 0193b53babe374bc7f8b0a0e42ea6544a68bd4920608261be5004c6db99437f05e021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 69aeea450b1a48352bdb84c9e602eb1bb9a22495ff6eb92e054fdf8ee39026d6 0.000600000000 1985423 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": 1495819, "vin": [ { "gen": { "height": 1495809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69aeea450b1a48352bdb84c9e602eb1bb9a22495ff6eb92e054fdf8ee39026d6" } } ], "extra": [ 1, 147, 181, 59, 171, 227, 116, 188, 127, 139, 10, 14, 66, 234, 101, 68, 166, 139, 212, 146, 6, 8, 38, 27, 229, 0, 76, 109, 185, 148, 55, 240, 94, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: