← previous blocknext block →recent activity
Analyzing
Block #83,454,862
23 transactions · 20 stateful · 2026-06-24 20:17:47 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,454,862 · 23 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
3w04w15w06w17w28w311w012w113w015w018w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xec06bf19…fcc3
0x34b655…2a6f
6 touches
3 conflicts
0x26731ffc…6b25
0x34b655…2a6f
6 touches
3 conflicts
0x126a0344…4465
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5e75a40f…5eed
0x34b655…2a6f
4 touches
1 conflict
0x60e2baf3…33d8
0x34b655…2a6f
4 touches
1 conflict
0x8b61212e…558e
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity