← previous blocknext block →recent activity
Analyzing
Block #83,635,457
20 transactions · 15 stateful · 2026-06-25 16:22:49 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,635,457 · 20 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
4w05w19w216w017w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7f1a44…eeeb
0x34b655…2a6f
6 touches
3 conflicts
0xe07d7921…dc35
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x95cb8e34…5eba
0x34b655…2a6f
4 touches
1 conflict
0x9a689fb3…ecf0
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xd3d708df…612c
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
3 conflicts on slot 0x2f7f1a44b5…3beeeb
Audit this contract →
← previous block·next block →recent activity