← previous blocknext block →recent activity
Analyzing
Block #83,356,092
18 transactions · 14 stateful · 2026-06-24 09:17:48 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,356,092 · 18 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
1w02w13w24w05w16w27w010w312w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x82684719…5269
0x065c9d…c394
4 touches
1 conflict
0x913ef5c5…d051
0x065c9d…c394
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0xfb0a4eb5…8be3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity