← previous blocknext block →recent activity
Analyzing
Block #105,852,589
23 transactions · 23 stateful · 2026-09-18 09:14:06 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,852,589 · 23 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
2w03w14w15w26w09w010w113w014w115w216w317w318w419w420w522w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaac0f5bb…f24a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xcaa1a41d…b844
0x34b655…2a6f
8 touches
6 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
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
6 conflicts on slot 0xaac0f5bb59…bef24a
Audit this contract →
← previous block·next block →recent activity