← previous blocknext block →recent activity
Analyzing
Block #83,493,143
11 transactions · 10 stateful · 2026-06-25 00:33:10 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,493,143 · 11 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
4w07w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02e5cdd…76b8
0x34b655…2a6f
6 touches
3 conflicts
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe515af89…8bab
0x34b655…2a6f
4 touches
1 conflict
0x2f9eb2d7…4254
0x34b655…2a6f
4 touches
1 conflict
0x05289bd6…9ab4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xa02e5cdd28…1376b8
Audit this contract →
← previous block·next block →recent activity