← previous blocknext block →recent activity
Analyzing
Block #106,917,069
35 transactions · 32 stateful · 2026-09-22 02:33:39 UTC
Parallelism
57/100
Blocked
53%
Avg conflicts / tx
2
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,917,069 · 35 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w09w113w014w115w216w317w418w519w620w721w822w923w1024w1125w1226w1327w1430w134w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
20 touches
45 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
18 touches
36 conflicts
0x1c0bf87d…7fae
0x34b655…2a6f
18 touches
36 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
14 touches
21 conflicts
0x8f4be1ed…2e29
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xa03832a9…e262
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
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
45 conflicts on slot 0xc8c615d41e…025da3
Audit this contract →
← previous block·next block →recent activity