← previous blocknext block →recent activity
Analyzing
Block #94,983,193
14 transactions · 12 stateful · 2026-08-11 05:54:26 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,983,193 · 14 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
2w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x025fef2f…9738
0x34b655…2a6f
2 touches
0 conflicts
0x09c7f797…408c
0x34b655…2a6f
2 touches
0 conflicts
0x154594d5…564e
0x34b655…2a6f
2 touches
0 conflicts
0x32c69201…e985
0x34b655…2a6f
2 touches
0 conflicts
0x3d2c514e…49b1
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity