← previous blocknext block →recent activity
Analyzing
Block #83,670,713
17 transactions · 17 stateful · 2026-06-25 20:18:02 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,670,713 · 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
2w03w17w28w39w014w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60872583…6452
0x34b655…2a6f
12 touches
15 conflicts
0x0f068b13…fb19
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe9d4d6d1…5158
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x65df2980…8edc
0x34b655…2a6f
4 touches
1 conflict
0x710fedfe…7f87
0x34b655…2a6f
4 touches
1 conflict
0x0843dc67…2db2
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
15 conflicts on slot 0x60872583da…b66452
Audit this contract →
← previous block·next block →recent activity