← previous blocknext block →recent activity
Analyzing
Block #93,328,134
12 transactions · 12 stateful · 2026-08-05 10:53:31 UTC
Parallelism
50/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,328,134 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x75e2d56c…19b3
0x34b655…2a6f
6 touches
3 conflicts
0x0c9322e4…9f1e
0x34b655…2a6f
6 touches
3 conflicts
0x1bd46462…e65c
0x34b655…2a6f
4 touches
1 conflict
0x4d0f5fd2…e6fe
0x34b655…2a6f
4 touches
1 conflict
0x6bd3cf03…b3eb
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
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 0x861e5aeffa…5cd32c
Audit this contract →
← previous block·next block →recent activity