← previous blocknext block →recent activity
Analyzing
Block #107,841,491
32 transactions · 29 stateful · 2026-09-25 08:09:03 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,841,491 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w010w011w113w114w215w316w017w118w120w121w222w323w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0a8c7a5…3422
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x99efd3f1…4e29
0xd32edf…ff58
7 touches
6 conflicts
0xcb2b8a75…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0xa0a8c7a55a…e73422
Audit this contract →
← previous block·next block →recent activity