← previous blocknext block →recent activity
Analyzing
Block #83,642,887
13 transactions · 13 stateful · 2026-06-25 17:12:27 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,642,887 · 13 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
2w04w17w28w09w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x403d1735…de44
0x34b655…2a6f
6 touches
3 conflicts
0xdefb1d04…7176
0x34b655…2a6f
4 touches
1 conflict
0x3823a798…22aa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 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
3 conflicts on slot 0x403d1735f4…68de44
Audit this contract →
← previous block·next block →recent activity