← previous blocknext block →recent activity
Analyzing
Block #102,280,642
23 transactions · 23 stateful · 2026-09-05 20:34:23 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,280,642 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w111w212w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0x908314bb…4574
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xbceecf11…0120
0x34b655…2a6f
5 touches
3 conflicts
0x6ea1896c…e070
0x34b655…2a6f
4 touches
1 conflict
0x7ad1b51a…14e7
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
3 conflicts on slot 0x53f7214d0d…cc8ec6
Audit this contract →
← previous block·next block →recent activity