← previous blocknext block →recent activity
Analyzing
Block #93,368,527
8 transactions · 7 stateful · 2026-08-05 14:16:36 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,368,527 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x896bf7d8…906b
0x34b655…2a6f
4 touches
1 conflict
0x1bbca09e…f873
0x34b655…2a6f
4 touches
1 conflict
0x013a6b08…d120
0x34b655…2a6f
2 touches
0 conflicts
0x042c4359…628d
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x18316bb4…d507
0x34b655…2a6f
2 touches
0 conflicts
0x1aae2384…15a6
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
3 conflicts on slot 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity