← previous blocknext block →recent activity
Analyzing
Block #83,655,187
23 transactions · 19 stateful · 2026-06-25 18:34:30 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,655,187 · 23 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
2w03w14w27w08w112w213w314w415w517w019w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c48b3ac…a03c
0x34b655…2a6f
10 touches
10 conflicts
0x52119c73…590c
0x34b655…2a6f
8 touches
6 conflicts
0xd064a456…b881
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x0d5dfba8…0b05
0x34b655…2a6f
6 touches
3 conflicts
0x487922c6…dbd2
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x1c48b3acf3…40a03c
Audit this contract →
← previous block·next block →recent activity