← previous blocknext block →recent activity
Analyzing
Block #106,568,653
39 transactions · 39 stateful · 2026-09-20 21:19:01 UTC
Parallelism
87/100
Blocked
18%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,568,653 · 39 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
2w03w14w15w232w033w234w136w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0xdce8be4e…082b
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
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 0x232b0b19e0…d1d946
Audit this contract →
← previous block·next block →recent activity