← previous blocknext block →recent activity
Analyzing
Block #83,411,086
25 transactions · 19 stateful · 2026-06-24 15:25:20 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,411,086 · 25 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
2w04w18w09w110w211w312w414w215w016w117w121w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x901d9f30…67a4
0x34b655…2a6f
8 touches
6 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0xec7b070f…db9a
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x604d1daf…bf48
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9d55b877…da3a
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity