← previous blocknext block →recent activity
Analyzing
Block #83,945,068
8 transactions · 8 stateful · 2026-06-27 02:48:09 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,945,068 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x0cbf85bc…5363
0x2ab50b…5c41
2 touches
0 conflicts
0x0d5b04cc…fe5f
0x2ab50b…5c41
2 touches
0 conflicts
0x16f4fddd…ed82
0x2ab50b…5c41
2 touches
0 conflicts
0x1e0f09ac…06a8
0x2ab50b…5c41
2 touches
0 conflicts
0x2b5a8e5f…a57c
0x2ab50b…5c41
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity