← previous blocknext block →recent activity
Analyzing
Block #105,600,619
25 transactions · 20 stateful · 2026-09-17 12:04:26 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,600,619 · 25 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
1w02w13w04w17w215w116w317w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bcfe5f…6c71
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x5fde4971…aac9
0x34b655…2a6f
8 touches
6 conflicts
0xcff4db4b…7052
0x34b655…2a6f
8 touches
6 conflicts
0xd587e8b9…f9f8
0x34b655…2a6f
8 touches
6 conflicts
0xd5b0b598…d859
0x34b655…2a6f
8 touches
6 conflicts
0xe708c9f4…b505
0x34b655…2a6f
8 touches
6 conflicts
0x4188cc5f…2d2e
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 0x38bcfe5f82…986c71
Audit this contract →
← previous block·next block →recent activity