← previous blocknext block →recent activity
Analyzing
Block #83,655,176
16 transactions · 15 stateful · 2026-06-25 18:34:26 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,655,176 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w714w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c48b3ac…a03c
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x6b1b2e40…fca6
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
10 touches
10 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xb6b7c45d…9d5a
0x34b655…2a6f
10 touches
10 conflicts
0xd064a456…b881
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x1c48b3acf3…40a03c
Audit this contract →
← previous block·next block →recent activity