← previous blocknext block →recent activity
Analyzing
Block #83,666,051
9 transactions · 8 stateful · 2026-06-25 19:46:55 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,666,051 · 9 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x7dc15f15…f94e
0x34b655…2a6f
2 touches
0 conflicts
0xb99958f6…ccf0
0x34b655…2a6f
2 touches
0 conflicts
0xb99958f6…ccf1
0x34b655…2a6f
2 touches
0 conflicts
0xf86f15cd…38af
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x6b47245e5d…eda342
Audit this contract →
← previous block·next block →recent activity