← previous blocknext block →recent activity
Analyzing
Block #83,652,263
17 transactions · 15 stateful · 2026-06-25 18:15:03 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,652,263 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w39w415w016w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b7c45d…9d5a
0x34b655…2a6f
12 touches
15 conflicts
0x6cdd3195…404f
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x74b52a70…e2f4
0x34b655…2a6f
6 touches
3 conflicts
0x74cc68f7…5134
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
6 touches
3 conflicts
0x85b5d985…d545
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xb6b7c45de7…c49d5a
Audit this contract →
← previous block·next block →recent activity