← previous blocknext block →recent activity
Analyzing
Block #83,890,333
20 transactions · 20 stateful · 2026-06-26 20:43:24 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,890,333 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w28w19w211w114w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x23ab8481…52d5
0x34b655…2a6f
4 touches
1 conflict
0x913ebf0e…d816
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity