← previous blocknext block →recent activity
Analyzing
Block #106,408,132
19 transactions · 19 stateful · 2026-09-20 07:51:06 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,408,132 · 19 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
1w02w03w14w06w19w116w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0xcf570cc1…b19c
0x99c7a7…8bf0
4 touches
1 conflict
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0xca841faa…486a
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity