← previous blocknext block →recent activity
Analyzing
Block #106,431,257
21 transactions · 17 stateful · 2026-09-20 09:47:29 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,431,257 · 21 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
1w02w03w14w111w215w316w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0xa96fec52…2ebd
0x34b655…2a6f
6 touches
3 conflicts
0x2507c7b7…58f7
0x34b655…2a6f
6 touches
3 conflicts
0x638b4c5d…0483
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x4bcbd0e7…5e26
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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity