← previous blocknext block →recent activity
Analyzing
Block #83,638,312
29 transactions · 27 stateful · 2026-06-25 16:41:55 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,638,312 · 29 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
1w02w13w05w16w27w38w09w110w011w112w213w214w315w319w220w421w427w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7500c6c7…6b90
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x44843215…109b
0x34b655…2a6f
4 touches
1 conflict
0x67252c71…3312
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
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 0x7500c6c7df…fe6b90
Audit this contract →
← previous block·next block →recent activity