← previous blocknext block →recent activity
Analyzing
Block #83,454,094
10 transactions · 8 stateful · 2026-06-24 20:12:39 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,454,094 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec06bf19…fcc3
0x34b655…2a6f
4 touches
1 conflict
0xffb1ee54…7c2c
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x1e32a320…0636
0x34b655…2a6f
2 touches
0 conflicts
0x288f0769…9e97
0x34b655…2a6f
2 touches
0 conflicts
0x2d95c7ff…1596
0x34b655…2a6f
2 touches
0 conflicts
0x31ea3bcf…ce1f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xec06bf1924…dffcc3
Audit this contract →
← previous block·next block →recent activity