← previous blocknext block →recent activity
Analyzing
Block #83,455,399
18 transactions · 13 stateful · 2026-06-24 20:21:22 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,455,399 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca8bab1…3957
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xdf37a93d…879b
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0xe936aca8…5f5e
0x34b655…2a6f
4 touches
1 conflict
0xa222991e…9179
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 0x6ca8bab118…113957
Audit this contract →
← previous block·next block →recent activity