← previous blocknext block →recent activity
Analyzing
Block #83,668,220
35 transactions · 26 stateful · 2026-06-25 20:01:25 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,668,220 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w211w012w117w018w119w220w021w122w223w327w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x3e776e71…4bbf
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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: Settlement / Helper
6 conflicts on slot 0xe02484a657…35c32e
Audit this contract →
← previous block·next block →recent activity