← previous blocknext block →recent activity
Analyzing
Block #83,624,999
14 transactions · 13 stateful · 2026-06-25 15:12:57 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,624,999 · 14 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
5w06w17w28w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xc2dcae88…f07a
0x34b655…2a6f
4 touches
1 conflict
0xc3464910…786f
0x34b655…2a6f
4 touches
1 conflict
0xd39c2a15…9006
0x34b655…2a6f
4 touches
1 conflict
0x6e1b71d7…8221
0x34b655…2a6f
4 touches
1 conflict
0xa2c66336…c4fb
0x34b655…2a6f
4 touches
1 conflict
0x31aa2853…8dbb
0xc8689a…ee79
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