← previous blocknext block →recent activity
Analyzing
Block #94,999,861
24 transactions · 21 stateful · 2026-08-11 07:18:16 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,999,861 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w09w110w211w312w413w315w116w222w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
14 touches
21 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0xcadd3e3d…4c15
0x065c9d…c394
4 touches
1 conflict
0x00d60c65…745d
0x34b655…2a6f
4 touches
1 conflict
0x1368ebc9…8095
0x34b655…2a6f
4 touches
1 conflict
0x7a8cad7f…48cd
0x34b655…2a6f
4 touches
1 conflict
0x802738ef…9072
0x34b655…2a6f
4 touches
1 conflict
0x9d6d235c…3d64
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
21 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity