← previous blocknext block →recent activity
Analyzing
Block #83,641,334
30 transactions · 27 stateful · 2026-06-25 17:02:05 UTC
Parallelism
73/100
Blocked
56%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,641,334 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w210w011w115w116w217w318w419w520w621w728w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity