← previous blocknext block →recent activity
Analyzing
Block #83,639,593
10 transactions · 10 stateful · 2026-06-25 16:50:27 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
1.1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,639,593 · 10 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
2w04w05w16w27w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x8f0e8a2f…a850
0x34b655…2a6f
8 touches
6 conflicts
0x93641233…06f5
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x10897d8d…9e5b
0x34b655…2a6f
4 touches
1 conflict
0x1741893b…c889
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity