← previous blocknext block →recent activity
Analyzing
Block #106,189,076
24 transactions · 22 stateful · 2026-09-19 13:28:36 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,189,076 · 24 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
1w02w13w24w05w16w17w28w310w414w516w517w618w722w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a29c64d…e772
0x34b655…2a6f
8 touches
6 conflicts
0xd41f5136…97c6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x6d43ee99…bdd9
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x05e1eba1…6491
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
6 conflicts on slot 0x1a29c64dd8…e6e772
Audit this contract →
← previous block·next block →recent activity