← previous blocknext block →recent activity
Analyzing
Block #93,300,753
11 transactions · 10 stateful · 2026-08-05 08:35:51 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,300,753 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x600ca1f7…b772
0x34b655…2a6f
4 touches
1 conflict
0x7c7eff13…16db
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x1f23d9ce…a001
0x34b655…2a6f
2 touches
0 conflicts
0x1fa0d08c…63b9
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity