← previous blocknext block →recent activity
Analyzing
Block #107,443,374
30 transactions · 24 stateful · 2026-09-23 22:43:10 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,443,374 · 30 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
1w02w03w18w110w014w015w017w120w121w123w024w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x3da6ec2b…b836
0x34b655…2a6f
4 touches
1 conflict
0x3e4486b9…fa99
0x34b655…2a6f
4 touches
1 conflict
0x0fd61128…b00b
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity