← previous blocknext block →recent activity
Analyzing
Block #107,440,738
19 transactions · 18 stateful · 2026-09-23 22:29:54 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,440,738 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w210w211w012w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88cf2d31…3d64
0x34b655…2a6f
10 touches
10 conflicts
0xddd9d39e…0c69
0x34b655…2a6f
8 touches
6 conflicts
0xfc8c9734…8019
0x34b655…2a6f
6 touches
3 conflicts
0xa3d78e5e…bb33
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb94a2ed9…d989
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
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
10 conflicts on slot 0x88cf2d3101…3b3d64
Audit this contract →
← previous block·next block →recent activity