← previous blocknext block →recent activity
Analyzing
Block #105,749,400
17 transactions · 17 stateful · 2026-09-18 00:33:20 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,749,400 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w39w110w212w013w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25b2a901…bace
0x34b655…2a6f
8 touches
6 conflicts
0xc5847c4d…a65c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x93d0f3c7…1813
0x40c49f…2af0
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0x7f7bf262…3534
0x34b655…2a6f
4 touches
1 conflict
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 0x25b2a90157…6bbace
Audit this contract →
← previous block·next block →recent activity