Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1decc7ed5a03ee340b6242ebd3993baab2af1423cf8df3c6d80ffb2b1fcad21

Tx prefix hash: 363feea68f97548eced2564522af39a559e119f2d669402edfa4d173a68571ad
Tx public key: aeb2b1ab0a068bed846823957a4c8cf0590b4927e6c486e4ca3525edea8c6f7f
Timestamp: 1774848215 Timestamp [UTC]: 2026-03-30 05:23:35 Age [y:d:h:m:s]: 00:233:18:07:22
Block: 1508867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172608 RingCT/type: yes/0
Extra: 01aeb2b1ab0a068bed846823957a4c8cf0590b4927e6c486e4ca3525edea8c6f7f021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7747bb78446f878b3b270142c6ee2dbb9c49264d4027f989d0585d09470d5577 0.000600000000 1998621 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": 1508877, "vin": [ { "gen": { "height": 1508867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7747bb78446f878b3b270142c6ee2dbb9c49264d4027f989d0585d09470d5577" } } ], "extra": [ 1, 174, 178, 177, 171, 10, 6, 139, 237, 132, 104, 35, 149, 122, 76, 140, 240, 89, 11, 73, 39, 230, 196, 134, 228, 202, 53, 37, 237, 234, 140, 111, 127, 2, 17, 0, 0, 0, 5, 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: