← previous blocknext block →recent activity
Analyzing
Block #83,455,415
24 transactions · 18 stateful · 2026-06-24 20:21:29 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,455,415 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w010w111w212w313w414w515w617w018w019w120w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x7fe12b88…aa1a
0x34b655…2a6f
8 touches
6 conflicts
0x126a0344…4465
0x34b655…2a6f
8 touches
6 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
6 touches
3 conflicts
0x6ca8bab1…3957
0x34b655…2a6f
4 touches
1 conflict
0x9b78bcf0…7955
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xe0336102…eaf2
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity