← previous blocknext block →recent activity
Analyzing
Block #107,450,106
50 transactions · 49 stateful · 2026-09-23 23:17:02 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,450,106 · 50 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w010w143w144w245w246w348w349w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7063105…100b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xc594c70a…9101
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x097cee83…0878
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
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 0xf70631053c…4e100b
Audit this contract →
← previous block·next block →recent activity