← previous blocknext block →recent activity
Analyzing
Block #102,246,143
25 transactions · 24 stateful · 2026-09-05 17:39:28 UTC
Parallelism
60/100
Blocked
54%
Avg conflicts / tx
1.6
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,246,143 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w09w110w211w318w419w520w621w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
10 touches
10 conflicts
0x225603d5…a2fb
0x34b655…2a6f
10 touches
10 conflicts
0x0110331c…b891
0x34b655…2a6f
8 touches
6 conflicts
0x17a7f697…dcb8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…00c9
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity