← previous blocknext block →recent activity
Analyzing
Block #107,442,020
19 transactions · 18 stateful · 2026-09-23 22:36:21 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,442,020 · 19 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
1w04w15w06w07w18w210w111w112w213w114w215w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd56cdf1…5168
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0x8fa4ba1b…750c
0x34b655…2a6f
6 touches
3 conflicts
0x61079029…0387
0x34b655…2a6f
6 touches
3 conflicts
0x189fbafb…47ca
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0xfd56cdf1a6…375168
Audit this contract →
← previous block·next block →recent activity