← previous blocknext block →recent activity
Analyzing
Block #83,621,806
23 transactions · 18 stateful · 2026-06-25 14:51:36 UTC
Parallelism
61/100
Blocked
61%
Avg conflicts / tx
0.96
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,621,806 · 23 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
1w03w04w18w09w110w211w312w413w515w118w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x90fefe5e…f0c6
0x34b655…2a6f
6 touches
3 conflicts
0x1e096ed6…1c7a
0x34b655…2a6f
4 touches
1 conflict
0x5fba4b48…16c0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
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