← previous blocknext block →recent activity
Analyzing
Block #105,619,256
32 transactions · 30 stateful · 2026-09-17 13:38:16 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.16
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,619,256 · 32 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w211w012w313w414w515w616w717w818w519w925w1028w1229w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e8f1bea…875b
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x012467fd…4237
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0x024f1167…7d7b
0x34b655…2a6f
8 touches
6 conflicts
0x6d787177…e955
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
28 conflicts on slot 0x5e8f1bea2a…0d875b
Audit this contract →
← previous block·next block →recent activity