← previous blocknext block →recent activity
Analyzing
Block #105,608,845
21 transactions · 18 stateful · 2026-09-17 12:45:51 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,608,845 · 21 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
2w03w14w05w17w08w19w210w313w314w415w516w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28a8cc9b…db4c
0x34b655…2a6f
14 touches
21 conflicts
0x953517cb…cdec
0x34b655…2a6f
10 touches
10 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
10 touches
10 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
21 conflicts on slot 0x28a8cc9b9d…76db4c
Audit this contract →
← previous block·next block →recent activity