← previous blocknext block →recent activity
Analyzing
Block #83,399,773
42 transactions · 23 stateful · 2026-06-24 14:09:45 UTC
Parallelism
90/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,399,773 · 42 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w227w028w130w231w336w237w140w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
6 touches
3 conflicts
0xbaff104b…3edb
0xa6afd3…d132
6 touches
3 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
6 touches
3 conflicts
0xf822d866…1214
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity