← previous blocknext block →recent activity
Analyzing
Block #106,935,473
29 transactions · 23 stateful · 2026-09-22 04:06:16 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,935,473 · 29 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
2w03w16w07w18w210w317w318w419w421w222w523w627w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe36a37be…b306
0x34b655…2a6f
12 touches
15 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
10 touches
10 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0x1084a1ad…8eb2
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xe36a37be51…0eb306
Audit this contract →
← previous block·next block →recent activity