← previous blocknext block →recent activity
Analyzing
Block #83,653,140
15 transactions · 14 stateful · 2026-06-25 18:20:55 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,653,140 · 15 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
1w02w13w04w19w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
10 touches
10 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
4 touches
1 conflict
0x9863393c…ce7b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd4702f73…926c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xddde2ffb…c029
0x34b655…2a6f
4 touches
1 conflict
0xfab623b3…e3de
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
10 conflicts on slot 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity