← previous blocknext block →recent activity
Analyzing
Block #82,736,563
16 transactions · 12 stateful · 2026-06-21 12:17:11 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,736,563 · 16 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
1w04w05w18w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dd2e140…b5f9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
4 touches
1 conflict
0x7dc06b7d…fc25
0x34b655…2a6f
4 touches
1 conflict
0x84b39dc4…bca6
0x34b655…2a6f
4 touches
1 conflict
0x961da181…ed17
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x5dd2e1401f…60b5f9
Audit this contract →
← previous block·next block →recent activity