← previous blocknext block →recent activity
Analyzing
Block #106,930,994
27 transactions · 27 stateful · 2026-09-22 03:43:44 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,930,994 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w09w110w011w112w213w314w215w316w417w518w619w720w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
16 touches
28 conflicts
0x643113d0…43d7
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd86a37ca…11c0
0x34b655…2a6f
8 touches
6 conflicts
0xeb30e223…4035
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
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
28 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity