← previous blocknext block →recent activity
Analyzing
Block #106,917,336
35 transactions · 34 stateful · 2026-09-22 02:34:59 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.57
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,917,336 · 35 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w08w19w110w211w312w413w514w615w716w217w118w219w320w821w922w1023w1124w1227w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
18 touches
36 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x251ee419…4404
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xc7ce92b1…25d0
0x34b655…2a6f
14 touches
21 conflicts
0x1d02654c…ff86
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity