← previous blocknext block →recent activity
Analyzing
Block #93,347,358
17 transactions · 17 stateful · 2026-08-05 12:30:10 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,347,358 · 17 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
1w03w07w08w110w211w313w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0xeb0ed9c8…5f39
0x34b655…2a6f
6 touches
3 conflicts
0x7281cd97…f967
0x34b655…2a6f
4 touches
1 conflict
0x93ed987d…ea03
0x34b655…2a6f
4 touches
1 conflict
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity