Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a91ac142fcbbae60457bfa17721580a13939a6bafb8d98e1ed957104638dfe95

Tx prefix hash: 8b388c65aca60d2954e21b20d39fde0f63d5146f55e59eb17e004fbbaa7907ee
Tx public key: 4eab207c222674ba741d96c6969aef3aeb202d8a8dac8b404ed731a547c41842
Timestamp: 1742265195 Timestamp [UTC]: 2025-03-18 02:33:15 Age [y:d:h:m:s]: 01:249:16:29:07
Block: 1241679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441815 RingCT/type: yes/0
Extra: 014eab207c222674ba741d96c6969aef3aeb202d8a8dac8b404ed731a547c41842021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c38eef12a31903c6300a506d72f898b26396f93f853d73cdf5f4c92f01c69334 0.000600000000 1728652 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": 1241689, "vin": [ { "gen": { "height": 1241679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c38eef12a31903c6300a506d72f898b26396f93f853d73cdf5f4c92f01c69334" } } ], "extra": [ 1, 78, 171, 32, 124, 34, 38, 116, 186, 116, 29, 150, 198, 150, 154, 239, 58, 235, 32, 45, 138, 141, 172, 139, 64, 78, 215, 49, 165, 71, 196, 24, 66, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: