← previous blocknext block →recent activity
Analyzing
Block #83,636,067
8 transactions · 8 stateful · 2026-06-25 16:26:54 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,636,067 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1526f9e…82d5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x057a2880…05c5
0x34b655…2a6f
4 touches
1 conflict
0x2d6ab761…405b
0x34b655…2a6f
2 touches
0 conflicts
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
0x34b655…2a6f
2 touches
0 conflicts
0x5fce1a8a…74f6
0x34b655…2a6f
2 touches
0 conflicts
0x7fe97198…79ab
0x34b655…2a6f
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
1 conflict on slot 0xc1526f9e7b…c282d5
Audit this contract →
← previous block·next block →recent activity