← previous blocknext block →recent activity
Analyzing
Block #83,401,678
34 transactions · 16 stateful · 2026-06-24 14:22:29 UTC
Parallelism
88/100
Blocked
56%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,401,678 · 34 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
1w02w17w022w023w124w125w226w329w130w232w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2004b5f1…ff98
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x967b4a40…7a78
0x34b655…2a6f
6 touches
3 conflicts
0xa7274f3f…63a8
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x5f1a616a…5b47
0x34b655…2a6f
4 touches
1 conflict
0x65bb8d8c…8bb0
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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
3 conflicts on slot 0x2004b5f102…a7ff98
Audit this contract →
← previous block·next block →recent activity