← previous blocknext block →recent activity
Analyzing
Block #94,469,310
16 transactions · 13 stateful · 2026-08-09 10:48:11 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,469,310 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w08w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x124e0be8…9d0f
0x34b655…2a6f
4 touches
1 conflict
0x19d0eecc…6863
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0x124e0be898…ae9d0f
Audit this contract →
← previous block·next block →recent activity