← previous blocknext block →recent activity
Analyzing
Block #83,617,288
22 transactions · 16 stateful · 2026-06-25 14:21:22 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,617,288 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w07w111w012w116w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
6 touches
3 conflicts
0x23ab8481…52d5
0x34b655…2a6f
6 touches
3 conflicts
0x5f3fc680…f989
0x34b655…2a6f
6 touches
3 conflicts
0x23c5c9ed…69bb
0x34b655…2a6f
6 touches
3 conflicts
0x708619a6…d52a
0x34b655…2a6f
4 touches
1 conflict
0x8a5efe9a…fa31
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity