← previous blocknext block →recent activity
Analyzing
Block #83,641,495
19 transactions · 16 stateful · 2026-06-25 17:03:09 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,641,495 · 19 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
4w07w08w19w210w313w314w415w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ae827f1…aa36
0x34b655…2a6f
12 touches
15 conflicts
0xda5e0705…ecb9
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6bcfbf05…c7fe
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
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
15 conflicts on slot 0x8ae827f129…5daa36
Audit this contract →
← previous block·next block →recent activity