← previous blocknext block →recent activity
Analyzing
Block #106,934,371
21 transactions · 21 stateful · 2026-09-22 04:00:44 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,934,371 · 21 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
1w02w03w15w06w19w010w112w013w114w216w217w018w319w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x715eeec8…5664
0x34b655…2a6f
6 touches
3 conflicts
0xacd9c381…91d1
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xa998841984…609f45
Audit this contract →
← previous block·next block →recent activity