← previous blocknext block →recent activity
Analyzing
Block #83,571,318
19 transactions · 18 stateful · 2026-06-25 09:14:32 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,571,318 · 19 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
1w02w13w24w26w07w18w214w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9863393c…ce7b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00966e54…7d1d
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
6 touches
3 conflicts
0x52d65d97…1c96
0xa6afd3…d132
6 touches
3 conflicts
0x231930a8…6b87
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
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
6 conflicts on slot 0x9863393ce4…4cce7b
Audit this contract →
← previous block·next block →recent activity