← previous blocknext block →recent activity
Analyzing
Block #106,187,086
19 transactions · 18 stateful · 2026-09-19 13:18:35 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,187,086 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w011w112w213w314w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0342bbf6…9683
0x6f6493…b480
8 touches
6 conflicts
0x2dfd9167…4109
0x6f6493…b480
8 touches
6 conflicts
0x37d024c9…5717
0x6f6493…b480
8 touches
6 conflicts
0x3a57b03b…9463
0x6f6493…b480
8 touches
6 conflicts
0x3d552957…2fbb
0x6f6493…b480
8 touches
6 conflicts
0x3f04af28…3e06
0x6f6493…b480
8 touches
6 conflicts
0x51466961…4fbc
0x6f6493…b480
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity