← previous blocknext block →recent activity
Analyzing
Block #106,549,019
20 transactions · 18 stateful · 2026-09-20 19:40:13 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,549,019 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c30bd77…61ae
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0xba65d335…5a78
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x07c47b1c…93c8
0x34b655…2a6f
4 touches
1 conflict
0x48711d1c…96ad
0x34b655…2a6f
2 touches
0 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7c30bd77e4…a861ae
Audit this contract →
← previous block·next block →recent activity