← previous blocknext block →recent activity
Analyzing
Block #94,478,016
10 transactions · 9 stateful · 2026-08-09 11:32:02 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,478,016 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0cd9fc1…1c44
0x34b655…2a6f
4 touches
1 conflict
0xc93761d9…cfdf
0x34b655…2a6f
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x6a46e23f…d28d
0x34b655…2a6f
2 touches
0 conflicts
0x6c084dcb…640c
0x34b655…2a6f
2 touches
0 conflicts
0x70eec2ed…f791
0x34b655…2a6f
2 touches
0 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc0cd9fc147…b21c44
Audit this contract →
← previous block·next block →recent activity