← previous blocknext block →recent activity
Analyzing
Block #83,455,073
24 transactions · 18 stateful · 2026-06-24 20:19:12 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,455,073 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w210w311w412w513w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4421e089…6f97
0x34b655…2a6f
4 touches
1 conflict
0x62554ce4…109e
0x34b655…2a6f
4 touches
1 conflict
0x6361660e…fd58
0x34b655…2a6f
4 touches
1 conflict
0x8d0e1d29…cd3e
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xc6a35453…7775
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity