← previous blocknext block →recent activity
Analyzing
Block #83,617,758
21 transactions · 20 stateful · 2026-06-25 14:24:31 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,617,758 · 21 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
1w02w04w05w16w27w38w49w110w115w016w117w218w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0x785889c9…0603
0x34b655…2a6f
6 touches
3 conflicts
0x003e3399…a0a5
0x34b655…2a6f
4 touches
1 conflict
0x07b47a10…27ef
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x251ca99b…3a93
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity