Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0968c78fc0459089be188128417f4d0c20d3dfcd2ee3b2bd5cb9ad38077de812

Tx prefix hash: dd1c465b5acffd19bacad5f2485b5fe0da01388a1fdda696abe36fea7bb4c38f
Tx public key: 60c76dd429c9e07d593923d15b83dd9fba0b0e105848c00c9647ddd9222755ff
Timestamp: 1705745578 Timestamp [UTC]: 2024-01-20 10:12:58 Age [y:d:h:m:s]: 02:118:17:55:07
Block: 939351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597038 RingCT/type: yes/0
Extra: 0160c76dd429c9e07d593923d15b83dd9fba0b0e105848c00c9647ddd9222755ff02110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f7562d0ed7ec3c325c3bcaf49cb82a9b9876b40ede00fdaf9074404ab67372a 0.000600000000 1397445 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": 939361, "vin": [ { "gen": { "height": 939351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7562d0ed7ec3c325c3bcaf49cb82a9b9876b40ede00fdaf9074404ab67372a" } } ], "extra": [ 1, 96, 199, 109, 212, 41, 201, 224, 125, 89, 57, 35, 209, 91, 131, 221, 159, 186, 11, 14, 16, 88, 72, 192, 12, 150, 71, 221, 217, 34, 39, 85, 255, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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: