← previous blocknext block →recent activity
Analyzing
Block #93,564,533
10 transactions · 9 stateful · 2026-08-06 06:41:59 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,564,533 · 10 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
2w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
2 touches
0 conflicts
0x35009efe…5217
0x34b655…2a6f
2 touches
0 conflicts
0x3ad8bbeb…b084
0x34b655…2a6f
2 touches
0 conflicts
0x3f5f366d…10d9
0x34b655…2a6f
2 touches
0 conflicts
0x4323fc7b…89b0
0x34b655…2a6f
2 touches
0 conflicts
0x560965b6…4603
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity