← previous blocknext block →recent activity
Analyzing
Block #83,633,609
26 transactions · 20 stateful · 2026-06-25 16:10:28 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,633,609 · 26 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
1w03w18w09w110w211w312w414w015w116w219w520w022w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x90a9e3f8…17ab
0x34b655…2a6f
6 touches
3 conflicts
0x993a283b…0f9e
0xd32edf…ff58
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x32329fca…2d8c
0x34b655…2a6f
4 touches
1 conflict
0x33412db4…0073
0x34b655…2a6f
4 touches
1 conflict
0x40040366…0faf
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity