← previous blocknext block →recent activity
Analyzing
Block #106,957,287
16 transactions · 16 stateful · 2026-09-22 05:56:05 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,957,287 · 16 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
1w03w04w15w26w17w28w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae76fcd2…d26a
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3e9bccd1…9cc9
0x34b655…2a6f
6 touches
3 conflicts
0x56755b2b…8d44
0x34b655…2a6f
6 touches
3 conflicts
0x5f72d58f…c445
0x34b655…2a6f
6 touches
3 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
6 touches
3 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
6 touches
3 conflicts
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 0xae76fcd240…64d26a
Audit this contract →
← previous block·next block →recent activity