← previous blocknext block →recent activity
Analyzing
Block #83,623,751
19 transactions · 13 stateful · 2026-06-25 15:04:37 UTC
Parallelism
74/100
Blocked
46%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,623,751 · 19 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
1w02w03w15w06w17w28w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71632345…6ee9
0x34b655…2a6f
8 touches
6 conflicts
0x0835adb5…ad83
0x34b655…2a6f
6 touches
5 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x051e5a8d…ca65
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd58b9a66…1c23
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
6 conflicts on slot 0x7163234506…a86ee9
Audit this contract →
← previous block·next block →recent activity