Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e5f70d0f5463f3648e41b2ed1fac6dc49531ea6f318d975bd7aaee50a0c8bb

Tx prefix hash: 7e6bb081e0e40f4f1d097ca5beab348973b046fc1a848f5560caa3a22838857c
Tx public key: 61bad22f50b362fd1c9e39b3c42d56d8b69b3bc324d2a629fe94f015425e6adf
Timestamp: 1772850415 Timestamp [UTC]: 2026-03-07 02:26:55 Age [y:d:h:m:s]: 00:253:04:56:28
Block: 1492344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186384 RingCT/type: yes/0
Extra: 0161bad22f50b362fd1c9e39b3c42d56d8b69b3bc324d2a629fe94f015425e6adf021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 26ced2204b5dffe1dd150cb0a02cbfb8d33b441f195f16a3ac659ede1979f829 0.000600000000 1981886 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": 1492354, "vin": [ { "gen": { "height": 1492344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26ced2204b5dffe1dd150cb0a02cbfb8d33b441f195f16a3ac659ede1979f829" } } ], "extra": [ 1, 97, 186, 210, 47, 80, 179, 98, 253, 28, 158, 57, 179, 196, 45, 86, 216, 182, 155, 59, 195, 36, 210, 166, 41, 254, 148, 240, 21, 66, 94, 106, 223, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: