← previous blocknext block →recent activity
Analyzing
Block #83,399,710
31 transactions · 28 stateful · 2026-06-24 14:09:20 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,399,710 · 31 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
2w04w07w19w010w111w012w113w015w118w019w120w221w225w127w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02e5cdd…76b8
0x34b655…2a6f
6 touches
3 conflicts
0x19a7003b…3615
0xd32edf…ff58
5 touches
3 conflicts
0x7f4b2b9b…3a00
0x065c9d…c394
4 touches
1 conflict
0xa3ff271e…db02
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xa02e5cdd28…1376b8
Audit this contract →
← previous block·next block →recent activity