← previous blocknext block →recent activity
Analyzing
Block #106,336,808
22 transactions · 19 stateful · 2026-09-20 01:52:09 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,336,808 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w110w012w214w115w016w117w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x33e0f63a…aca0
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0xb90556e3…0e6a
0x34b655…2a6f
4 touches
1 conflict
0x3a4929f2…71f2
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity