← previous blocknext block →recent activity
Analyzing
Block #83,671,113
17 transactions · 13 stateful · 2026-06-25 20:20:42 UTC
Parallelism
65/100
Blocked
46%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,671,113 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w39w411w514w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
10 touches
10 conflicts
0xbaedc843…8f5f
0x34b655…2a6f
8 touches
6 conflicts
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x913ebf0e…d816
0x34b655…2a6f
6 touches
3 conflicts
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x54afc6e5…cde2
0x34b655…2a6f
4 touches
1 conflict
0x65df2980…8edc
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
10 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity