← previous blocknext block →recent activity
Analyzing
Block #105,619,871
35 transactions · 34 stateful · 2026-09-17 13:41:22 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,619,871 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w010w112w013w115w420w222w329w432w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9660902a…a12b
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0xda54eaa7…5736
0x34b655…2a6f
8 touches
6 conflicts
0x6d787177…e955
0x34b655…2a6f
6 touches
3 conflicts
0xf346808d…6ad4
0x34b655…2a6f
6 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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 0x9660902a7f…cba12b
Audit this contract →
← previous block·next block →recent activity