← previous blocknext block →recent activity
Analyzing
Block #82,271,795
21 transactions · 20 stateful · 2026-06-19 08:32:37 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,271,795 · 21 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
4w05w17w18w09w112w214w217w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9365e097…ff56
0x34b655…2a6f
6 touches
3 conflicts
0x9cc13b7b…c0ac
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09012a11…ac6a
0x34b655…2a6f
4 touches
1 conflict
0x463be44a…2830
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 0x9365e0978e…fbff56
Audit this contract →
← previous block·next block →recent activity