← previous blocknext block →recent activity
Analyzing
Block #106,271,954
30 transactions · 27 stateful · 2026-09-19 20:25:48 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,271,954 · 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
1w02w14w05w16w17w214w016w121w222w323w424w525w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x10648fe8…cc34
0x34b655…2a6f
8 touches
6 conflicts
0x51f1f20c…d9da
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
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 0x3b6e959d6b…f8158f
Audit this contract →
← previous block·next block →recent activity