← previous blocknext block →recent activity
Analyzing
Block #83,668,526
14 transactions · 13 stateful · 2026-06-25 20:03:27 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,668,526 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w49w510w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3a2ac17…465e
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x24d68cf2…09b7
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x65df2980…8edc
0x34b655…2a6f
8 touches
6 conflicts
0xcbc0533a…f4e4
0x34b655…2a6f
8 touches
6 conflicts
0xd4702f73…926c
0x34b655…2a6f
8 touches
6 conflicts
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
15 conflicts on slot 0xd3a2ac177b…68465e
Audit this contract →
← previous block·next block →recent activity