← previous blocknext block →recent activity
Analyzing
Block #83,631,851
21 transactions · 18 stateful · 2026-06-25 15:58:43 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,631,851 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w07w18w213w314w115w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e346a85…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0xdb19247d…233c
0x34b655…2a6f
4 touches
1 conflict
0xeafe6a27…79cc
0x34b655…2a6f
4 touches
1 conflict
0xf5970b31…f34c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3470392b…1b05
0x40c49f…2af0
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 0x1e346a85f5…1ee9c5
Audit this contract →
← previous block·next block →recent activity