← previous blocknext block →recent activity
Analyzing
Block #93,228,937
10 transactions · 7 stateful · 2026-08-05 02:34:46 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,228,937 · 10 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
2w03w14w25w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe9c95e…de7c
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x282f129e…8f33
0x34b655…2a6f
4 touches
1 conflict
0x2b6b57d4…7587
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3f4f9f22…8ad7
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
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
3 conflicts on slot 0xfbe9c95e9b…39de7c
Audit this contract →
← previous block·next block →recent activity