← previous blocknext block →recent activity
Analyzing
Block #93,466,131
14 transactions · 13 stateful · 2026-08-05 22:27:19 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,466,131 · 14 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
4w05w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37a
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
6 touches
3 conflicts
0x13ae2a4c…2ee0
0x34b655…2a6f
4 touches
1 conflict
0x7ce5b49a…237c
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0x1c622ef7…a617
0x34b655…2a6f
3 touches
1 conflict
0xf9f616f1…7a0e
0x34b655…2a6f
3 touches
1 conflict
0x0d528651…72f0
0x754704…b603
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
3 conflicts on slot 0x4e8c4408ae…50d37a
Audit this contract →
← previous block·next block →recent activity