← previous blocknext block →recent activity
Analyzing
Block #107,823,326
22 transactions · 22 stateful · 2026-09-25 06:37:37 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,326 · 22 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
2w03w14w27w09w110w311w213w314w415w516w617w720w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x6b97ded2…f70b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x7ed4080f…0f62
0x34b655…2a6f
6 touches
3 conflicts
0x261261a7…6175
0x1b6862…e19c
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
10 conflicts on slot 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity