← previous blocknext block →recent activity
Analyzing
Block #83,455,772
16 transactions · 13 stateful · 2026-06-24 20:23:52 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,455,772 · 16 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
4w05w06w17w210w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb147eeb0…d658
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0xa0daddf2…7a50
0x34b655…2a6f
4 touches
1 conflict
0xba3e0ef0…ba9e
0x34b655…2a6f
4 touches
1 conflict
0xdf37a93d…879b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0xb147eeb07e…40d658
Audit this contract →
← previous block·next block →recent activity