← previous blocknext block →recent activity
Analyzing
Block #83,455,892
15 transactions · 11 stateful · 2026-06-24 20:24:40 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,455,892 · 15 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
4w05w16w29w311w012w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2b18bf…d24e
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0x26731ffc…6b25
0x34b655…2a6f
4 touches
1 conflict
0x2a2702d3…e7cb
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x910be0f4…b71c
0x34b655…2a6f
4 touches
1 conflict
0xfebf4166…9bf2
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
6 conflicts on slot 0x7a2b18bfee…11d24e
Audit this contract →
← previous block·next block →recent activity