← previous blocknext block →recent activity
Analyzing
Block #83,655,664
28 transactions · 22 stateful · 2026-06-25 18:37:42 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,655,664 · 28 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
1w02w13w29w210w011w112w213w018w019w123w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f7ad3a0…de3b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0x144746d7…edcc
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe4c6b0cb…0a23
0x1b6862…e19c
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
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
3 conflicts on slot 0x3f7ad3a0be…58de3b
Audit this contract →
← previous block·next block →recent activity