← previous blocknext block →recent activity
Analyzing
Block #83,638,763
26 transactions · 16 stateful · 2026-06-25 16:44:54 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,638,763 · 26 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
13w014w115w016w017w121w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffb1ee54…7c2c
0x34b655…2a6f
8 touches
6 conflicts
0x0ce059c0…00d5
0x34b655…2a6f
4 touches
1 conflict
0x13729aba…1444
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x2f4d415d…5f95
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x70063dd1…39cb
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 0xffb1ee5457…d07c2c
Audit this contract →
← previous block·next block →recent activity