← previous blocknext block →recent activity
Analyzing
Block #94,491,135
15 transactions · 13 stateful · 2026-08-09 12:38:01 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,491,135 · 15 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
1w02w13w04w15w16w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x80656e3b…9240
0x34b655…2a6f
6 touches
3 conflicts
0x70eec2ed…f791
0x34b655…2a6f
6 touches
3 conflicts
0x511f4d1c…65c9
0x34b655…2a6f
4 touches
1 conflict
0x6530927f…68be
0x34b655…2a6f
4 touches
1 conflict
0x6e2b56d3…be86
0x34b655…2a6f
4 touches
1 conflict
0x803eb45d…00bd
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity