← previous blocknext block →recent activity
Analyzing
Block #106,042,506
22 transactions · 20 stateful · 2026-09-19 01:10:59 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,042,506 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w18w29w310w411w513w616w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5dd033b6…34b5
0x34b655…2a6f
4 touches
1 conflict
0x662e354e…e306
0x34b655…2a6f
4 touches
1 conflict
0x6c51b6e5…91e1
0x34b655…2a6f
4 touches
1 conflict
0xa26ad34d…bc02
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity