← previous blocknext block →recent activity
Analyzing
Block #107,847,644
20 transactions · 16 stateful · 2026-09-25 08:40:01 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,847,644 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w110w211w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xb54ff07e…e41d
0x34b655…2a6f
4 touches
1 conflict
0xbe512d56…38f2
0x34b655…2a6f
4 touches
1 conflict
0xf75c3a6b…0568
0x34b655…2a6f
4 touches
1 conflict
0x0b223a4f…8fe0
0x34b655…2a6f
4 touches
1 conflict
0x3750b746…5a9e
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
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
3 conflicts on slot 0xecff7c3510…111b43
Audit this contract →
← previous block·next block →recent activity