← previous blocknext block →recent activity
Analyzing
Block #94,051,664
14 transactions · 13 stateful · 2026-08-07 23:31:45 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,051,664 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w38w09w110w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39a80e6d…021a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xac2d6d91…73ce
0xa6afd3…d132
5 touches
3 conflicts
0x41c16dcc…78ab
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x39a80e6d81…64021a
Audit this contract →
← previous block·next block →recent activity