← previous blocknext block →recent activity
Analyzing
Block #81,878,206
37 transactions · 30 stateful · 2026-06-17 12:46:06 UTC
Parallelism
81/100
Blocked
73%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #81,878,206 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w210w211w312w413w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
12 touches
15 conflicts
0x74f95963…01a2
0x34b655…2a6f
10 touches
10 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x826cce18…251c
0x34b655…2a6f
6 touches
3 conflicts
0xa72e521d…f873
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
15 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity