← previous blocknext block →recent activity
Analyzing
Block #83,412,759
18 transactions · 14 stateful · 2026-06-24 15:36:31 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,412,759 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w18w29w311w012w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xd06d821c…e5d0
0x34b655…2a6f
6 touches
3 conflicts
0x02faae16…a5eb
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x3c9bce0e…0440
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x73cc3662…c52b
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
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