← previous blocknext block →recent activity
Analyzing
Block #81,626,892
35 transactions · 28 stateful · 2026-06-16 08:51:38 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.66
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,626,892 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w08w010w011w112w214w115w221w022w023w324w325w132w033w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x897df0ee…b0c5
0x40c49f…2af0
8 touches
6 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
8 touches
6 conflicts
0x1017e868…fcc2
0x34b655…2a6f
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
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: 0x40c49f17…d22af0
6 conflicts on slot 0x897df0ee4f…0cb0c5
Audit this contract →
← previous block·next block →recent activity