← previous blocknext block →recent activity
Analyzing
Block #83,615,705
30 transactions · 24 stateful · 2026-06-25 14:10:47 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,615,705 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w07w18w29w310w114w015w116w217w323w024w325w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f3fc680…f989
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x606bcc2b…3377
0x34b655…2a6f
6 touches
3 conflicts
0x708619a6…d52a
0x34b655…2a6f
4 touches
1 conflict
0xade99311…13fd
0x34b655…2a6f
4 touches
1 conflict
0xb3c96942…f0fc
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 0x5f3fc68024…49f989
Audit this contract →
← previous block·next block →recent activity