← previous blocknext block →recent activity
Analyzing
Block #106,054,266
57 transactions · 55 stateful · 2026-09-19 02:10:09 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,054,266 · 57 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
1w02w14w05w18w09w112w213w351w454w355w456w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x5dabd855…8ffb
0x34b655…2a6f
4 touches
1 conflict
0x65e5696a…6a0d
0x34b655…2a6f
4 touches
1 conflict
0x73894a77…8136
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity