← previous blocknext block →recent activity
Analyzing
Block #106,916,991
41 transactions · 41 stateful · 2026-09-22 02:33:15 UTC
Parallelism
46/100
Blocked
73%
Avg conflicts / tx
4.02
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #106,916,991 · 41 txs across 22 waves · depth 22
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
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w09w310w413w114w415w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
26 touches
78 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
20 touches
45 conflicts
0xccebf5c5…8758
0x34b655…2a6f
20 touches
45 conflicts
0x6e33e6d3…8f78
0x34b655…2a6f
18 touches
36 conflicts
0x69411fb3…e36d
0x34b655…2a6f
18 touches
36 conflicts
0xf1bbd371…e541
0x34b655…2a6f
14 touches
21 conflicts
0x3a0218bf…e2a3
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
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 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity