← previous blocknext block →recent activity
Analyzing
Block #107,823,085
20 transactions · 19 stateful · 2026-09-25 06:36:25 UTC
Parallelism
55/100
Blocked
53%
Avg conflicts / tx
1.75
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,823,085 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w39w110w411w512w613w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
16 touches
28 conflicts
0xbf04c2e6…2636
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
8 touches
6 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaa1757b8…50de
0x34b655…2a6f
6 touches
3 conflicts
0x15a642a7…3b84
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 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity