← previous blocknext block →recent activity
Analyzing
Block #93,671,402
11 transactions · 8 stateful · 2026-08-06 15:39:14 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,671,402 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
0x34b655…2a6f
4 touches
1 conflict
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0x16e1bce0…73a5
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x12bde66e…6b12
0x34b655…2a6f
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 0x69ee34d107…a730f8
Audit this contract →
← previous block·next block →recent activity