← previous blocknext block →recent activity
Analyzing
Block #83,210,362
14 transactions · 11 stateful · 2026-06-23 17:04:29 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,210,362 · 14 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
4w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
8 touches
6 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0x8d594c28…9c52
0x34b655…2a6f
5 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x502cf5ae…ae86
0x34b655…2a6f
3 touches
1 conflict
0x8f8639bd…f483
0x34b655…2a6f
3 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
6 conflicts on slot 0x6f132c01d5…7dcdcd
Audit this contract →
← previous block·next block →recent activity