← previous blocknext block →recent activity
Analyzing
Block #106,187,144
30 transactions · 30 stateful · 2026-09-19 13:18:53 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,187,144 · 30 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
2w03w14w25w06w110w011w112w013w215w316w417w524w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x019264d7…c75b
0x34b655…2a6f
8 touches
6 conflicts
0x997ae611…3591
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x31aa604c…cf32
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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 0x019264d787…00c75b
Audit this contract →
← previous block·next block →recent activity