← previous blocknext block →recent activity
Analyzing
Block #107,816,436
17 transactions · 15 stateful · 2026-09-25 06:02:57 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,816,436 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
16 touches
28 conflicts
0x4cd7fdf4…7197
0x34b655…2a6f
14 touches
21 conflicts
0xc10b903d…2f54
0x34b655…2a6f
12 touches
15 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xb6039eff…b0d1
0x34b655…2a6f
8 touches
6 conflicts
0xaa97569b…1480
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity