← previous blocknext block →recent activity
Analyzing
Block #107,815,181
17 transactions · 16 stateful · 2026-09-25 05:56:38 UTC
Parallelism
53/100
Blocked
44%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,815,181 · 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
5w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x740fff9f…4244
0x34b655…2a6f
12 touches
15 conflicts
0xdc16b418…2f5d
0x34b655…2a6f
6 touches
3 conflicts
0x4ac770b4…8b4c
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x09a43d55…7c20
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0x6a3f702a…be68
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
21 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity