Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95045f010d3b1983926a7ec0a092072f92bc667589bb65161df2e239a85621c7

Tx prefix hash: 2930feb1b8d4f92e6a2dc42c8100ecf35436b8ddd1ffb6e67845a6062cc67d7e
Tx public key: 93769e23bc0fc71cee7d3b267a7290f49e4a2bb1947cb92e0f994039e99594bb
Timestamp: 1709419348 Timestamp [UTC]: 2024-03-02 22:42:28 Age [y:d:h:m:s]: 02:261:23:17:02
Block: 969840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712356 RingCT/type: yes/0
Extra: 0193769e23bc0fc71cee7d3b267a7290f49e4a2bb1947cb92e0f994039e99594bb0211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5074440214329316933d9230b8ced66cc800a82d85529e2e48c5444d52d39365 0.000600000000 1429689 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": 969850, "vin": [ { "gen": { "height": 969840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5074440214329316933d9230b8ced66cc800a82d85529e2e48c5444d52d39365" } } ], "extra": [ 1, 147, 118, 158, 35, 188, 15, 199, 28, 238, 125, 59, 38, 122, 114, 144, 244, 158, 74, 43, 177, 148, 124, 185, 46, 15, 153, 64, 57, 233, 149, 148, 187, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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: