← previous blocknext block →recent activity
Analyzing
Block #83,570,863
19 transactions · 19 stateful · 2026-06-25 09:11:31 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,570,863 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w27w08w19w210w312w014w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x40c9380a…2115
0xa6afd3…d132
6 touches
3 conflicts
0x52d65d97…1c96
0xa6afd3…d132
6 touches
3 conflicts
0xd3752858…c7dd
0x34b655…2a6f
6 touches
3 conflicts
0xdeddb1c8…0d40
0x34b655…2a6f
6 touches
3 conflicts
0x5596b935…cc30
0x34b655…2a6f
4 touches
1 conflict
0xf6a2695a…ab52
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity