← previous blocknext block →recent activity
Analyzing
Block #102,313,607
36 transactions · 31 stateful · 2026-09-05 23:21:22 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.64
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #102,313,607 · 36 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w07w18w19w210w315w421w522w724w325w833w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89656ac5…5173
0x34b655…2a6f
16 touches
28 conflicts
0x22f10271…841d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1d351a9b…f2dd
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
28 conflicts on slot 0x89656ac5bf…555173
Audit this contract →
← previous block·next block →recent activity