← previous blocknext block →recent activity
Analyzing
Block #83,655,731
16 transactions · 12 stateful · 2026-06-25 18:38:08 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,655,731 · 16 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
4w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c53a187…3646
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x70eb3e6b…db43
0x34b655…2a6f
8 touches
6 conflicts
0xd064a456…b881
0x34b655…2a6f
8 touches
6 conflicts
0xe6fd65c0…3a8a
0x34b655…2a6f
6 touches
3 conflicts
0x735c4044…dbbd
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x2c53a187ea…bc3646
Audit this contract →
← previous block·next block →recent activity