← previous blocknext block →recent activity
Analyzing
Block #93,406,113
12 transactions · 11 stateful · 2026-08-05 17:25:35 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,406,113 · 12 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
1w02w04w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x73320e64…b06f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x01bae8a2…d116
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x25e65ccc…c735
0x34b655…2a6f
2 touches
0 conflicts
0x2840c278…bbc7
0x34b655…2a6f
2 touches
0 conflicts
0x39aa73f3…34bb
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 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity