← previous blocknext block →recent activity
Analyzing
Block #83,890,776
14 transactions · 12 stateful · 2026-06-26 20:46:21 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,890,776 · 14 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
1w03w06w17w28w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e346a85…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0x2dfe0d73…9685
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0000
0x16d564…365f
2 touches
0 conflicts
0x00000000…0002
0x16d564…365f
2 touches
0 conflicts
0x00000000…0008
0x16d564…365f
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
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 0x1e346a85f5…1ee9c5
Audit this contract →
← previous block·next block →recent activity