← previous blocknext block →recent activity
Analyzing
Block #106,916,623
47 transactions · 42 stateful · 2026-09-22 02:31:24 UTC
Parallelism
64/100
Blocked
76%
Avg conflicts / tx
2.87
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,916,623 · 47 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w18w29w311w412w515w516w324w625w726w827w928w1039w240w641w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0x5969523e…5191
0x34b655…2a6f
14 touches
21 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
14 touches
21 conflicts
0x75e4cee9…0731
0x34b655…2a6f
14 touches
21 conflicts
0x76832384…dc5b
0x34b655…2a6f
14 touches
21 conflicts
0xa03832a9…e262
0x34b655…2a6f
14 touches
21 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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity