← previous blocknext block →recent activity
Analyzing
Block #83,979,713
9 transactions · 8 stateful · 2026-06-27 06:38:59 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,979,713 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8279ae9…f9f9
0x34b655…2a6f
4 touches
1 conflict
0x2b657c98…3f92
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x55382911…56fc
0x34b655…2a6f
2 touches
0 conflicts
0x581b829b…9578
0x34b655…2a6f
2 touches
0 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
2 touches
0 conflicts
0xbcf4c53f…eed0
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 0xa8279ae941…15f9f9
Audit this contract →
← previous block·next block →recent activity