← previous blocknext block →recent activity
Analyzing
Block #105,617,273
48 transactions · 42 stateful · 2026-09-17 13:28:17 UTC
Parallelism
71/100
Blocked
64%
Avg conflicts / tx
1.48
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,617,273 · 48 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w18w09w110w211w312w413w514w115w623w130w231w235w237w338w439w540w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b595a5d…894c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x4e135144…4167
0x34b655…2a6f
8 touches
6 conflicts
0x55b553fa…d66c
0x34b655…2a6f
8 touches
6 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
8 touches
6 conflicts
0xbbe2df09…d681
0x34b655…2a6f
8 touches
6 conflicts
0xd5398303…808b
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x6b595a5d7d…1f894c
Audit this contract →
← previous block·next block →recent activity