← previous blocknext block →recent activity
Analyzing
Block #83,495,214
13 transactions · 13 stateful · 2026-06-25 00:46:55 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,495,214 · 13 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
4w05w16w27w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bd818fc…4f86
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0x992c1cec…8263
0x34b655…2a6f
4 touches
1 conflict
0x89f2822c…00da
0x34b655…2a6f
4 touches
1 conflict
0x282b7895…9a08
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 0x5bd818fcf8…714f86
Audit this contract →
← previous block·next block →recent activity