← previous blocknext block →recent activity
Analyzing
Block #83,666,030
19 transactions · 15 stateful · 2026-06-25 19:46:46 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,666,030 · 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
6w09w110w212w313w014w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x478e6e08…83bf
0x34b655…2a6f
10 touches
10 conflicts
0x16dce2e7…6f05
0x34b655…2a6f
6 touches
3 conflicts
0x0823ad11…d862
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdf37a93d…879b
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
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 0x478e6e0871…8083bf
Audit this contract →
← previous block·next block →recent activity