← previous blocknext block →recent activity
Analyzing
Block #82,391,418
10 transactions · 6 stateful · 2026-06-19 21:51:06 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,391,418 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xab83f300…f8c8
0x34b655…2a6f
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x70248bfb…cb24
0x065c9d…c394
2 touches
0 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x26abe30c…f680
0x34b655…2a6f
2 touches
0 conflicts
0x385a54e0…61ec
0x34b655…2a6f
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity