← previous blocknext block →recent activity
Analyzing
Block #83,665,811
11 transactions · 9 stateful · 2026-06-25 19:45:18 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,665,811 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dce2e7…6f05
0x34b655…2a6f
4 touches
1 conflict
0xb6b7c45d…9d5a
0x34b655…2a6f
4 touches
1 conflict
0xdf199ec5…f082
0x34b655…2a6f
4 touches
1 conflict
0xf86f15cd…38af
0x34b655…2a6f
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b416
0x928dc8…8207
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
1 conflict on slot 0x16dce2e7df…1b6f05
Audit this contract →
← previous block·next block →recent activity