← previous blocknext block →recent activity
Analyzing
Block #83,467,520
8 transactions · 7 stateful · 2026-06-24 21:42:21 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,467,520 · 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70eb3e6b…db43
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x126a0344…4465
0x34b655…2a6f
2 touches
0 conflicts
0x1f50fd2c…91dd
0x34b655…2a6f
2 touches
0 conflicts
0x4d98a8ff…87f3
0x34b655…2a6f
2 touches
0 conflicts
0x8b305a3b…1c35
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 0x70eb3e6bb3…56db43
Audit this contract →
← previous block·next block →recent activity