← previous blocknext block →recent activity
Analyzing
Block #93,187,809
21 transactions · 20 stateful · 2026-08-04 23:08:00 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,187,809 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w210w311w413w516w217w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d38d5e0…a06c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
6 touches
3 conflicts
0x772ab420…c2f6
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37a
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
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
10 conflicts on slot 0x4d38d5e0a9…6ca06c
Audit this contract →
← previous block·next block →recent activity