← previous blocknext block →recent activity
Analyzing
Block #83,661,761
18 transactions · 16 stateful · 2026-06-25 19:18:18 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,661,761 · 18 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
4w05w16w17w28w39w411w215w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7f1a44…eeeb
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x95cb8e34…5eba
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 conflicts
0xe1e1d73b…1081
0x34b655…2a6f
6 touches
3 conflicts
0x016bc958…9f94
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
15 conflicts on slot 0x2f7f1a44b5…3beeeb
Audit this contract →
← previous block·next block →recent activity