← previous blocknext block →recent activity
Analyzing
Block #81,621,821
20 transactions · 17 stateful · 2026-06-16 08:17:51 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,621,821 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w210w011w112w314w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0xd5e4013d…a383
0x34b655…2a6f
6 touches
3 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity