← previous blocknext block →recent activity
Analyzing
Block #82,208,476
29 transactions · 19 stateful · 2026-06-19 01:30:10 UTC
Parallelism
90/100
Blocked
26%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,208,476 · 29 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
1w02w14w06w011w115w224w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x71a5f74f…7c8d
0xd32edf…ff58
5 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x85946e90…7fd6
0x0c65a0…0852
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity