← previous blocknext block →recent activity
Analyzing
Block #82,328,372
22 transactions · 16 stateful · 2026-06-19 14:49:57 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,328,372 · 22 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
1w02w15w09w011w113w115w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x6836c701…a656
0x34b655…2a6f
4 touches
1 conflict
0x73f16822…0338
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 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity