← previous blocknext block →recent activity
Analyzing
Block #83,638,852
16 transactions · 15 stateful · 2026-06-25 16:45:30 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,638,852 · 16 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
2w03w18w29w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
10 touches
10 conflicts
0xb1c2f30f…7c83
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x1b1df992…40eb
0x34b655…2a6f
4 touches
1 conflict
0x1d146248…a0d9
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x8f0e8a2f…a850
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
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 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity