← previous blocknext block →recent activity
Analyzing
Block #83,671,091
14 transactions · 13 stateful · 2026-06-25 20:20:33 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,671,091 · 14 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
2w03w15w06w27w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913ebf0e…d816
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xde696e46…6446
0x34b655…2a6f
8 touches
6 conflicts
0x5ecbbb8a…c1cd
0x34b655…2a6f
6 touches
3 conflicts
0xfd840ce3…51e3
0x34b655…2a6f
6 touches
3 conflicts
0x68c6b2fa…098d
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x54837e4d…ab95
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
15 conflicts on slot 0x913ebf0e0a…d2d816
Audit this contract →
← previous block·next block →recent activity