← previous blocknext block →recent activity
Analyzing
Block #93,229,028
11 transactions · 11 stateful · 2026-08-05 02:35:14 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,229,028 · 11 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
1w02w03w16w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb35e663e…354e
0x34b655…2a6f
4 touches
1 conflict
0x770ea029…2ca6
0x34b655…2a6f
4 touches
1 conflict
0x861e5aef…d32c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2bd4c467…ae85
0x34b655…2a6f
4 touches
1 conflict
0x046e4d12…847a
0x34b655…2a6f
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x0eac7709…66c3
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 0xb35e663ea0…22354e
Audit this contract →
← previous block·next block →recent activity