← previous blocknext block →recent activity
Analyzing
Block #107,443,942
20 transactions · 19 stateful · 2026-09-23 22:46:01 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,443,942 · 20 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
1w02w14w25w06w37w48w010w112w113w415w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1af
0x37db7f…ec7b
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfc8c9734…8019
0x34b655…2a6f
6 touches
3 conflicts
0xdb0c84d4…b094
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ae
0x37db7f…ec7b
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3da6ec2b…b836
0x34b655…2a6f
6 touches
3 conflicts
0x163d1c6f…311d
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: 0x37db7fbf…3eec7b
10 conflicts on slot 0x8a35acfbc1…6bd1af
Audit this contract →
← previous block·next block →recent activity