← previous blocknext block →recent activity
Analyzing
Block #82,159,948
24 transactions · 19 stateful · 2026-06-18 20:06:57 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,159,948 · 24 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
1w02w13w04w27w09w010w112w116w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73f16822…0338
0x34b655…2a6f
6 touches
3 conflicts
0x2662ba77…9b3c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xda8aabb2…c5af
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
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 0x73f16822f0…380338
Audit this contract →
← previous block·next block →recent activity