← previous blocknext block →recent activity
Analyzing
Block #106,932,860
43 transactions · 40 stateful · 2026-09-22 03:53:08 UTC
Parallelism
70/100
Blocked
70%
Avg conflicts / tx
2.21
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,932,860 · 43 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
1w02w13w24w37w08w110w011w112w213w314w415w519w620w721w822w923w1024w1125w1233w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
16 touches
28 conflicts
0x0463db49…5d05
0x34b655…2a6f
16 touches
28 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
14 touches
21 conflicts
0x4db5cc0f…1368
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0x94e7f277…471b
0x34b655…2a6f
14 touches
21 conflicts
0xf75d2778…4de5
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity