← previous blocknext block →recent activity
Analyzing
Block #83,628,303
39 transactions · 36 stateful · 2026-06-25 15:35:01 UTC
Parallelism
62/100
Blocked
69%
Avg conflicts / tx
3.54
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,628,303 · 39 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w08w09w110w211w312w415w016w117w218w319w420w521w622w723w824w925w1029w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x4ed3af20…d87d
0x34b655…2a6f
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xaa7ee7…f0e4
10 touches
10 conflicts
0x0b408000…9df1
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity