← previous blocknext block →recent activity
Analyzing
Block #106,924,238
37 transactions · 36 stateful · 2026-09-22 03:09:44 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
2.19
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,924,238 · 37 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
1w02w03w17w18w29w312w213w314w415w516w617w718w820w121w922w1023w1124w1225w1326w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4230a60…bd13
0x34b655…2a6f
20 touches
45 conflicts
0xba1edffb…323e
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xbbb93c5b…db1b
0x34b655…2a6f
14 touches
21 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
14 touches
21 conflicts
0x8cc85946…0e47
0x34b655…2a6f
8 touches
6 conflicts
0x6a8d403c…3e46
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
45 conflicts on slot 0xd4230a6034…58bd13
Audit this contract →
← previous block·next block →recent activity