← previous blocknext block →recent activity
Analyzing
Block #93,555,611
10 transactions · 7 stateful · 2026-08-06 05:57:08 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,555,611 · 10 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x3d0a1339…f545
0x34b655…2a6f
4 touches
1 conflict
0x225c7832…e0f5
0x34b655…2a6f
2 touches
0 conflicts
0x31fd9aa9…e0fc
0x34b655…2a6f
2 touches
0 conflicts
0x36e7818c…c2ea
0x34b655…2a6f
2 touches
0 conflicts
0x16632078…27d5
0xea1b8e…c5ec
2 touches
0 conflicts
0x6eff5416…605d
0xea1b8e…c5ec
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 0x628359b1c9…1a7263
Audit this contract →
← previous block·next block →recent activity