← previous blocknext block →recent activity
Analyzing
Block #105,848,975
24 transactions · 23 stateful · 2026-09-18 08:55:54 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,848,975 · 24 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
1w02w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20fcad1f…1d7d
0x34b655…2a6f
16 touches
28 conflicts
0x97e4c862…4419
0x34b655…2a6f
14 touches
21 conflicts
0x606df28e…ad1b
0x6f6493…b480
10 touches
10 conflicts
0xd07bc4e2…e834
0x6f6493…b480
10 touches
10 conflicts
0x5ea120d3…f4e8
0x6f6493…b480
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
10 touches
10 conflicts
0xffd30cc8…08d1
0x6f6493…b480
10 touches
10 conflicts
0xe65c0fa8…8dff
0x6f6493…b480
10 touches
10 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 0x20fcad1fc4…ee1d7d
Audit this contract →
← previous block·next block →recent activity