← previous blocknext block →recent activity
Analyzing
Block #105,634,525
16 transactions · 15 stateful · 2026-09-17 14:55:09 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,634,525 · 16 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
1w02w03w14w26w110w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b6550bf…9bd2
0x34b655…2a6f
12 touches
15 conflicts
0xab41643c…f9bf
0x34b655…2a6f
10 touches
10 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
8 touches
6 conflicts
0x86bd79a5…1f48
0x34b655…2a6f
6 touches
3 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0x5a1b27dd…f076
0x34b655…2a6f
4 touches
1 conflict
0xfa6b44d9…ef79
0x34b655…2a6f
4 touches
1 conflict
0x1b25d785…ea84
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
15 conflicts on slot 0x7b6550bf0c…379bd2
Audit this contract →
← previous block·next block →recent activity