← previous blocknext block →recent activity
Analyzing
Block #93,674,458
30 transactions · 28 stateful · 2026-08-06 15:54:35 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,674,458 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w07w18w09w110w211w313w415w518w119w222w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6af3bfab…17a8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf1e2f456…7422
0x34b655…2a6f
6 touches
3 conflicts
0xfdd569bb…af08
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
15 conflicts on slot 0x6af3bfabb5…f117a8
Audit this contract →
← previous block·next block →recent activity