Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d09791ad4428ccf5018b94edca01e3ef1a51b7e485229b27798e73cdc4d44ac4

Tx prefix hash: 57964d93a8a5cc3575595f96cbc74dd5ac9a037bef8c6aad89cf87b9551530a7
Tx public key: c6886e66c3eccf40c57f14c424bb42343e2fb20fb9548df7b59f84ae2467ec59
Timestamp: 1630842303 Timestamp [UTC]: 2021-09-05 11:45:03 Age [y:d:h:m:s]: 05:078:09:30:51
Block: 327912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1355582 RingCT/type: yes/0
Extra: 01c6886e66c3eccf40c57f14c424bb42343e2fb20fb9548df7b59f84ae2467ec5902110000020abaa4486c000000000000000000

1 output(s) for total of 0.050291185223 xmr

stealth address amount amount idx tag
00: 00a3cac5d41ec4c8aaef9b7bcaf4e5035e4ec4101c0b61548d51abaa0e94e992 0.050291185223 678929 of 0 -

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": 327922, "vin": [ { "gen": { "height": 327912 } } ], "vout": [ { "amount": 50291185223, "target": { "key": "00a3cac5d41ec4c8aaef9b7bcaf4e5035e4ec4101c0b61548d51abaa0e94e992" } } ], "extra": [ 1, 198, 136, 110, 102, 195, 236, 207, 64, 197, 127, 20, 196, 36, 187, 66, 52, 62, 47, 178, 15, 185, 84, 141, 247, 181, 159, 132, 174, 36, 103, 236, 89, 2, 17, 0, 0, 2, 10, 186, 164, 72, 108, 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: