← previous blocknext block →recent activity
Analyzing
Block #83,571,512
11 transactions · 11 stateful · 2026-06-25 09:15:50 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,571,512 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85ac0ab8…a3d8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4467ecee…e95b
0x34b655…2a6f
4 touches
1 conflict
0x1b2c54a1…5a76
0x34b655…2a6f
3 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x2aa98b05…31ef
0x34b655…2a6f
2 touches
0 conflicts
0xc967cba9…5259
0x34b655…2a6f
2 touches
0 conflicts
0xe64e6363…e676
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x85ac0ab8d3…aaa3d8
Audit this contract →
← previous block·next block →recent activity