← previous blocknext block →recent activity
Analyzing
Block #106,921,943
31 transactions · 30 stateful · 2026-09-22 02:58:11 UTC
Parallelism
58/100
Blocked
77%
Avg conflicts / tx
2.58
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,921,943 · 31 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
1w02w13w24w36w07w18w29w310w411w513w614w715w816w917w1018w1119w1220w422w429w930w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
16 touches
28 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xa725b52a…4a88
0x34b655…2a6f
14 touches
21 conflicts
0xf7ed92bb…24eb
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 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 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity