← previous blocknext block →recent activity
Analyzing
Block #83,634,859
8 transactions · 6 stateful · 2026-06-25 16:18:49 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,634,859 · 8 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
1w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x672fd8ba…9e9e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x505f101e…7ad6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1d3b9dd6…9681
0x34b655…2a6f
4 touches
1 conflict
0x24e133eb…b3c5
0x34b655…2a6f
2 touches
0 conflicts
0x50a44bf8…d65b
0x34b655…2a6f
2 touches
0 conflicts
0x590e82c0…6dd2
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x672fd8ba57…cf9e9e
Audit this contract →
← previous block·next block →recent activity