← previous blocknext block →recent activity
Analyzing
Block #107,440,928
17 transactions · 17 stateful · 2026-09-23 22:30:51 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
1.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,440,928 · 17 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
1w02w03w14w25w16w07w28w19w310w211w413w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb205bed7…d507
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8acd7e07…049b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1af
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
6 touches
3 conflicts
0x8d5914d7…8eba
0x34b655…2a6f
4 touches
1 conflict
0xa3d78e5e…bb33
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 0xb205bed793…43d507
Audit this contract →
← previous block·next block →recent activity