← previous blocknext block →recent activity
Analyzing
Block #106,801,500
21 transactions · 19 stateful · 2026-09-21 16:51:57 UTC
Parallelism
71/100
Blocked
26%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,801,500 · 21 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
2w03w15w27w39w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4a98226…0332
0x34b655…2a6f
8 touches
6 conflicts
0x6f5d7ccd…83d4
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x30ff13df…5326
0x34b655…2a6f
4 touches
1 conflict
0x38594928…2c55
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x83123fae…e98d
0x34b655…2a6f
4 touches
1 conflict
0x8a02d049…f481
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 0xd4a982261c…010332
Audit this contract →
← previous block·next block →recent activity