← previous blocknext block →recent activity
Analyzing
Block #83,483,719
12 transactions · 12 stateful · 2026-06-24 23:30:21 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,483,719 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xbab709eb…1a5c
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xfe4e62b8…9ade
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x69df8a…6292
2 touches
0 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
3 conflicts on slot 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity