← previous blocknext block →recent activity
Analyzing
Block #83,639,895
16 transactions · 15 stateful · 2026-06-25 16:52:28 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,639,895 · 16 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
3w04w16w17w28w39w410w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x93641233…06f5
0x34b655…2a6f
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
6 touches
3 conflicts
0x8f0e8a2f…a850
0x34b655…2a6f
6 touches
3 conflicts
0x7e6c970a…65af
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x7f8763d2…1510
0x34b655…2a6f
4 touches
1 conflict
0x00966e54…7d1d
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