← previous blocknext block →recent activity
Analyzing
Block #82,018,722
24 transactions · 13 stateful · 2026-06-18 04:24:49 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,018,722 · 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
1w02w13w06w112w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c59b8c…89c0
0x34b655…2a6f
4 touches
1 conflict
0x07cab7ef…ef28
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x1e266251…015c
0x40c49f…2af0
2 touches
0 conflicts
0x2ea1e982…7041
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0x06c59b8c41…2989c0
Audit this contract →
← previous block·next block →recent activity