← previous blocknext block →recent activity
Analyzing
Block #106,192,790
22 transactions · 21 stateful · 2026-09-19 13:47:17 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,192,790 · 22 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
1w02w13w04w17w29w010w311w412w113w514w615w016w118w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95fb9c30…63ad
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
6 touches
3 conflicts
0x766c0128…5cb9
0x34b655…2a6f
6 touches
3 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
6 touches
3 conflicts
0xb66366c3…fc81
0x34b655…2a6f
6 touches
3 conflicts
0xc1a4c088…e828
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
10 conflicts on slot 0x95fb9c30f3…8263ad
Audit this contract →
← previous block·next block →recent activity