← previous blocknext block →recent activity
Analyzing
Block #107,666,655
30 transactions · 24 stateful · 2026-09-24 17:28:15 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,666,655 · 30 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
6w07w18w29w113w214w321w424w326w427w528w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b76a1fb…fdfc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd95ed05c…acca
0x34b655…2a6f
6 touches
3 conflicts
0xb1bc7bc9…3c43
0x34b655…2a6f
4 touches
1 conflict
0xe098738f…9bbe
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
10 conflicts on slot 0x2b76a1fb53…5afdfc
Audit this contract →
← previous block·next block →recent activity